Re: 'make check' failure in gcc-3.3 in x86->x86 cross build. How to debug dejagnu usage problems?

[Dan Kegel]

Dan Kegel wrote:
> So here's the question: what's the best way to figure out dejagnu 
> problems like this?
> My usual tools - find -name '*.exp', xarg, grep, a big printout, and a 
> cross-reference - aren't helping enough.
> I did see when I read through the source that there is a built-in debugger.
> (I imagine I could set a breakpoint on setenv, say.)
> When dejagnu wizards are tracking problems down, do they use the 
> debugger, or what?

Next chance I get, I'll try inserting an 'env' right before runtest
gets run, too, to make sure the shell script isn't the one setting
LD_LIBRARY_PATH.  Didn't think of that before wiping the directory.

I should mention that I appreciate how responsive Rob appears to
be on the mailing list.  It's gotta be hard what with whiny users
like me around :-)
- Dan

--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045