This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Pierre, You can run command (below) on your own machine: gdb -batch --eval "info shared" binary core 2> /dev/null |\ sed -n -e 's/^.*Yes[^\/]*\//\//p' -e 's/^.*No[^\/]*\//\//p' > filelist and then do cat filelist | zip zipme.zip -@ on client's one. PS: this small article might be helpful. http://www.samersoff.net/do/index.php/blog/19-articles/56-how-to-open-java-coredump-in-gdb -Dmitry On 07/13/2017 12:24 PM, Pierre Ossman wrote: > Hi, > > I'd like to see if there is a way to produce binaries so that gdb can > walk the stack in a core dump even if the libraries gdb sees doesn't > match the libraries when the core dump was generated. > > My scenario is simply that we might get crashes at customer sites. > Rather than getting some kind of remote access up an running, it would > be easier to have them send us a core dump from the crash. We then load > the core file together with a binary with debug symbols on our end. > > Unfortunately gdb doesn't traverse the stack correctly if the crash is > in a system library. We just get random addresses for each frame. > > It's okay that we cannot get the proper symbols or local variables for > frames that are in system libraries, but is there some way to get access > to the frames that are in our binary? > > Regards
Attachment:
signature.asc
Description: OpenPGP digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |