Date: Tue, 29 Oct 2002 15:40:42 -0800 (PST) From: Nate Lawson <nate@root.org> To: Zhihui Zhang <zzhang@cs.binghamton.edu> Cc: freebsd-hackers@freebsd.org Subject: RE: Command used to trace the stack of a process Message-ID: <Pine.BSF.4.21.0210291539240.88401-100000@root.org> In-Reply-To: <Pine.SOL.4.21.0210291816580.6268-100000@onyx>
next in thread | previous in thread | raw e-mail | index | archive | help
l *routine + 0x350 or if you use a core file with symbols (-g), gdb will do it automatically. Please read the gdb docs for better info. On Tue, 29 Oct 2002, Zhihui Zhang wrote: > > Thanks. The backtrace often gives something like: > > <routine name> + 0x350 > > Is there a way to quickly determine the correponding source code line? > > -Zhihui > > On Tue, 29 Oct 2002, Nate Lawson wrote: > > > On Tue, 29 Oct 2002, John Baldwin wrote: > > > On 29-Oct-2002 Zhihui Zhang wrote: > > > > > > > > I remember there is a command in either gdb or ddb which enable you to > > > > display the stack of a particular process. Can anyone tell me if there is > > > > such a command and what the command is? Thanks! > > > > > > In ddb you can do 'tr <pid>' where <pid> is the PID of the process. > > > > In gdb, it's bt. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0210291539240.88401-100000>