From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-28105-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 20642 invoked by alias); 13 Mar 2007 05:22:15 -0000
Received: (qmail 20633 invoked by uid 22791); 13 Mar 2007 05:22:14 -0000
X-Spam-Check-By: sourceware.org
Received: from ug-out-1314.google.com (HELO ug-out-1314.google.com) (66.249.92.175)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 13 Mar 2007 05:22:09 +0000
Received: by ug-out-1314.google.com with SMTP id 75so133870ugb         for <gdb@sourceware.org>; Mon, 12 Mar 2007 22:22:06 -0700 (PDT)
Received: by 10.114.25.3 with SMTP id 3mr2242878way.1173763325001;         Mon, 12 Mar 2007 22:22:05 -0700 (PDT)
Received: from ?192.168.2.37? ( [222.66.14.54])         by mx.google.com with ESMTP id z20sm19358403pod.2007.03.12.22.21.56;         Mon, 12 Mar 2007 22:22:04 -0700 (PDT)
Message-ID: <45F634E2.4020205@gmail.com>
Date: Tue, 13 Mar 2007 05:22:00 -0000
From: Bin Chen <binary.chen@gmail.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20070103)
MIME-Version: 1.0
To: Rich Rattanni <rattanni@gmail.com>
CC:  gdb@sourceware.org, Bin Chen <binary.chen@gmail.com>
Subject: Re: Cause of the ?? in backtrace
References: <3187bd480703120747h332fbf12gab39d77719c910f9@mail.gmail.com>
In-Reply-To: <3187bd480703120747h332fbf12gab39d77719c910f9@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2007-03/txt/msg00183.txt.bz2

Rich Rattanni 写道:
> 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
> Cannot access memory at address 0x30 <------------|
> (gdb)
>
Just FYI. Last time I encounter such problem and I found that it is not 
caused with your private code didn't compile with -g, but is caused by 
your common libc related library didn't contain the debug info.