On Sun, Feb 25, 2007 at 01:14:44AM -0800, Steve Langasek wrote: > Looking at the code, I gather that it's expected for this test to throw an > assertion, and the problem is that it blows up on the other end. Other > tests that use CPPUNIT_ASSERT_ASSERTION_FAIL() seem to work ok, though, so > it doesn't seem to be a general problem with exception handling on alpha. > I'll dig a bit further and see what I can see.
Well, debugging this is pretty non-trivial. I've figured out that parse_lsda_header() is used for "language-specific data" in the objects that the exception is being generated for, but half of the activity for this happens within libgcc, for which no debugging version is available. I've tried rebuilding cppunit itself with different -g options (-gstabs, or without -g at all) to see if that would have any effect; it didn't. Still bombs out at the same place. Ah, but building with -O0 does the trick -- so there's a workaround for you if you'd care to go with that. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]