Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Shiv Prashant Sood <Shiv_PS@huawei.com>
To: gdb@sourceware.org
Subject: cryptic stack trace!
Date: Wed, 23 May 2007 10:01:00 -0000	[thread overview]
Message-ID: <002001c79d21$52b677c0$d408120a@china.huawei.com> (raw)

Hi All,

At times the stack trace done using gdb shows a cryptic output. e.g.

(gdb) bt 3
#0  0x4d709681 in ?? ()
#1  0x4d8d5854 in ?? ()
#2  0x4d70705c in ?? ()

I also get a warning saying
"warning: current_sos: Can't read pathname for load map: Input/output error"

I want to know why this problem occurs and what should i do to get 
non-cryptic output(with function names).

In case the question is not appropriate for this forum please redirect me to 
a forum where i can get GDB usage help.

Regards,
Shiv

"Duniya Maast Kalander!
Te ute baitha Bandar, Samghe aapno Sikandar.
Tu ChaK De Phathe."



             reply	other threads:[~2007-05-23 10:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 10:01 Shiv Prashant Sood [this message]
2007-05-23 10:58 ` Dharmosoth Seetharam
2007-05-23 11:00   ` Dharmosoth Seetharam

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='002001c79d21$52b677c0$d408120a@china.huawei.com' \
    --to=shiv_ps@huawei.com \
    --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