From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-9706-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 9758 invoked by alias); 26 Jul 2002 17:03:29 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 9746 invoked from network); 26 Jul 2002 17:03:28 -0000
Received: from unknown (HELO zwingli.cygnus.com) (208.245.165.35)
  by sources.redhat.com with SMTP; 26 Jul 2002 17:03:28 -0000
Received: by zwingli.cygnus.com (Postfix, from userid 442)
	id 5210A5EA11; Fri, 26 Jul 2002 12:03:27 -0500 (EST)
To: "Lucy Zhang" <lucyz@uclink4.berkeley.edu>
Cc: <gdb@sources.redhat.com>
Subject: Re: how does GDB find the symbols?
References: <004501ea8fb2$e33da4c0$9a0a0109@zhangl>
	<20020724160422.GA5346@nevyn.them.org> <3D3EE3D4.9030502@ixiacom.com>
	<20020724185743.GA14821@nevyn.them.org> <3D3F05C2.8050200@ixiacom.com>
	<001f01ea907b$e385b7f0$9a0a0109@zhangl>
	<20020725161857.GB10993@nevyn.them.org>
	<011f01c23444$1de51c90$9a0a0109@zhangl>
From: Jim Blandy <jimb@redhat.com>
Date: Fri, 26 Jul 2002 10:03:00 -0000
In-Reply-To: <011f01c23444$1de51c90$9a0a0109@zhangl>
Message-ID: <np8z3ys9pd.fsf@zwingli.cygnus.com>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-SW-Source: 2002-07/txt/msg00283.txt.bz2


"Lucy Zhang" <lucyz@uclink4.berkeley.edu> writes:
> I'm converting a coredump into the ELF format. At first, the outputs in GDB
> came out blank, i.e.
> #0 0x40091aa5 in ?? ()
> 
> 
> But after I added some other infomation, now I get the symbols filled in.
> i.e.
> 
> #0 0x40091aa5 in sigset (sig=-1073747472, disp=0x20) at
>     ../sysdeps/posix/sigset.c:69
> 
> Where does GDB find the function names, the arg lists, and other such
> information?

>From the executable file's debugging info.