From: Joel Brobecker <brobecker@adacore.com>
To: Rich Rattanni <rattanni@gmail.com>
Cc: Michael Snyder <Michael.Snyder@palmsource.com>, gdb@sourceware.org
Subject: Re: Cause of the ?? in backtrace
Date: Tue, 13 Mar 2007 04:07:00 -0000 [thread overview]
Message-ID: <20070313040804.GQ14401@adacore.com> (raw)
In-Reply-To: <3187bd480703122048v4b1482f0n1cffd1f473af5193@mail.gmail.com>
> 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?
Building it with -g should be sufficient. However, even if the library
was not built with debug info, we should still have the symbol table
to work with, right?
One thing you can do to confirm whether the address is legitimate or
not, is check the instruction just before 0x47de97e0 (that's the
return address). If it is not a jump or a call, then I'm pretty
sure the problem is in the computing of that return address...
> 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
--
Joel
next prev parent reply other threads:[~2007-03-13 4:07 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
2007-03-13 4:07 ` Joel Brobecker [this message]
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=20070313040804.GQ14401@adacore.com \
--to=brobecker@adacore.com \
--cc=Michael.Snyder@palmsource.com \
--cc=gdb@sourceware.org \
--cc=rattanni@gmail.com \
/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