Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pierre Ossman <ossman@cendio.se>
To: gdb@sourceware.org
Subject: Decoding stack in core file without correct libs?
Date: Thu, 13 Jul 2017 09:25:00 -0000	[thread overview]
Message-ID: <197a6eed-6163-67ed-67b7-57c4298d851b@cendio.se> (raw)

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
-- 
Pierre Ossman           Software Development
Cendio AB               https://cendio.com
Teknikringen 8          https://twitter.com/ThinLinc
583 30 Linköping        https://facebook.com/ThinLinc
Phone: +46-13-214600    https://plus.google.com/+CendioThinLinc

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?


             reply	other threads:[~2017-07-13  9:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13  9:25 Pierre Ossman [this message]
2017-07-13  9:55 ` Dmitry Samersoff
2017-07-13 10:21   ` Pierre Ossman
2017-07-13 15:22 ` Jan Kratochvil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=197a6eed-6163-67ed-67b7-57c4298d851b@cendio.se \
    --to=ossman@cendio.se \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox