RE: Command used to trace the stack of a process

On 29-Oct-2002 Nate Lawson wrote: 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. You can also use 'nm' with grep to find routine's start address. Then add the offset to that and use 'addr2line' to find

Re: Command used to trace the stack of a process

Is /usr/ports/sysutils/pstack what you're looking for? -- Peter. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message

RE: Command used to trace the stack of a process

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

RE: Command used to trace the stack of a process

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

RE: Command used to trace the stack of a process

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

RE: Command used to trace the stack of a process

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