On Fri, Nov 13, 2009 at 05:57:49PM +0100, Eugeniy Meshcheryakov wrote: > 13 ????????? 2009 ? 15:21 +0100 Kurt Roeckx ???????(-??): > > So my understanding of the code is that it gets a list of path's > > to look at. It does: > > const Dwfl_Callbacks *const cb = mod->dwfl->callbacks; > > char *path = strdupa ((cb->debuginfo_path ? *cb->debuginfo_path : NULL) > > ?: DEFAULT_DEBUGINFO_PATH); > > > > And the default is: > > libdwflP.h:#define DEFAULT_DEBUGINFO_PATH ":.debug:/usr/lib/debug" > > > > systemtap seems to be changing the debuginfo_path. > Yes, it changes it to "+:.debug:/usr/lib/debug:build" or to > $SYSTEMTAP_DEBUGINFO_PATH if it is set. I tried to set > SYSTEMTAP_DEBUGINFO_PATH to different values and found that libdw stops > trying to open files after empty directory. For example it finds > debuginfo (and crashes systemtap) if i remove first colon. Or move it to > the end. Comment in find-debuginfo.c says: > /* An empty entry says to try the main file's directory. */ > So systemtap's debuginfo_path looks correct.
So I'm guessing that it opens the file in /lib/modules/ calls the validate() function which says it was succesful, while the file actually doesn't have any debug info? I assume that systemtap crashing is some other (non-related) problem? Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
