On 04/12/2015, Gregory Farnum wrote:
> I must be missing something here. As far as I can tell, "throw
> FailedAssertion" only happens in assert.cc, and I know that stuff
> doesn't destroy the relevant stack frames since I've pulled the info
> out of core dumps when debugging?
> -Greg
The behavior I'm seeing is that when I am attached to a process with gdb, and
an assertion fails it bounces all the way up to terminate with an uncaught
exception.
--
Senior Software Engineer Red Hat Storage, Ann Arbor, MI, US
IRC: Aemerson@{RedHat, OFTC, Freenode}
0x80F7544B90EDBFB9 E707 86BA 0C1B 62CC 152C 7C12 80F7 544B 90ED BFB9
Attachment:
signature.asc
Description: PGP signature
