From: "Rich Rattanni" <rattanni@gmail.com>
To: "Michael Snyder" <Michael.Snyder@palmsource.com>
Cc: gdb@sourceware.org
Subject: Re: Cause of the ?? in backtrace
Date: Tue, 13 Mar 2007 03:48:00 -0000 [thread overview]
Message-ID: <3187bd480703122048v4b1482f0n1cffd1f473af5193@mail.gmail.com> (raw)
In-Reply-To: <1173744387.11051.24.camel@localhost.localdomain>
In order to ensure the library has debug info built into it, do you
just need to build the library with the -g option specified during
compilation? Or is it more involved?
On 3/12/07, Michael Snyder <Michael.Snyder@palmsource.com> wrote:
> On Mon, 2007-03-12 at 10:47 -0400, Rich Rattanni wrote:
> > Why would one get the following when trying to do a backtrace in GDB...
> > (gdb) bt
> > #0 0x403cdcb4 in _int_malloc () from /lib/libc.so.6
> > #1 0x403cedfc in malloc () from /lib/libc.so.6
> > #2 0x401c4418 in sqlite3MallocRaw () from /usr/lib/libsqlite3.so.0
> > #3 0x401c450c in sqlite3StrNDup () from /usr/lib/libsqlite3.so.0
> > #4 0x401cc070 in sqlite3VdbeChangeP3 () from /usr/lib/libsqlite3.so.0
> > #5 0x401cc0ac in sqlite3VdbeOp3 () from /usr/lib/libsqlite3.so.0
> > #6 0x401ac010 in sqlite3CodeSubselect () from /usr/lib/libsqlite3.so.0
> > #7 0x401ab4b0 in sqlite3ExprCode () from /usr/lib/libsqlite3.so.0
> > #8 0x401abd00 in sqlite3ExprIfFalse () from /usr/lib/libsqlite3.so.0
> > #9 0x401d02cc in sqlite3WhereBegin () from /usr/lib/libsqlite3.so.0
> > #10 0x401bf13c in sqlite3Select () from /usr/lib/libsqlite3.so.0
> > #11 0x401b6978 in sqlite3Parser () from /usr/lib/libsqlite3.so.0
> > #12 0x401c12e0 in sqlite3RunParser () from /usr/lib/libsqlite3.so.0
> > #13 0x47de97e0 in ?? () <------------------------------- This
> > is my problem
>
>
> Specifically, the ?? means that gdb could not find a symbol to
> correspond with the instruction address 0x47de97e0. This might
> mean any number of things.
>
> If the address is legitimate (ie. the return address of sqlite3RunParser
> really does point back to a caller at 0x47de97e0), then this caller
> may be from a library for which gdb has no symbols. It might be
> self-generating code, in which case it may never have had any
> symbols.
>
> Or the address may NOT be legitimate, and may have come about
> as a result of a corrupted stack or something.
>
>
next prev parent reply other threads:[~2007-03-13 3:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 14:48 Rich Rattanni
2007-03-12 14:52 ` Daniel Jacobowitz
2007-03-13 0:06 ` Michael Snyder
2007-03-13 3:48 ` Rich Rattanni [this message]
2007-03-13 4:07 ` Joel Brobecker
2007-03-13 9:15 ` Andreas Schwab
2007-03-13 5:22 ` Bin Chen
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=3187bd480703122048v4b1482f0n1cffd1f473af5193@mail.gmail.com \
--to=rattanni@gmail.com \
--cc=Michael.Snyder@palmsource.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