cvs commit: src/sys/bus/usb usb_ethersubr.c src/sys/kern kern_poll.c uipc_msg.c src/sys/net netisr.c netisr.h src/sys/net/ppp if_ppp.c src/sys/netgraph/netgraph ng_base.c src/sys/netinet if_ether.c ip_demux.c ip_input.c tcp_subr.c ...

YONETANI Tomokazu qhwt+dragonfly-commits at
Wed Apr 14 04:14:10 PDT 2004

On Tue, Apr 13, 2004 at 12:34:59PM -0700, Matthew Dillon wrote:
> :By the way, is there a way to specify from which process to show the
> :trace in gdb -k? For example, mpd had pid 36 in the above trace, but
> :if I manually panic, savecore the dump and feed it to gdb -k, I don't
> :know how to specify the pid in gdb. It's too late to simply set a
> :breakpoint on lwkt_default_waitport after mpd got stuck because, but
> :if I set the breakpoint BEFORE mpd hangs, maybe I have to skip too
> :many false-positives before reaching the target.
>     Yes, you should be able to specify the pid:
>     gdb> proc 27
>     gdb> back

I tried this, but gdb says `invalid proc address' for any existing pids,
and `invalid pid' for non-existent process. Specifying thread structure
address always seems to work though.
>     For pure threads, supply the address of the thread structure.
>     gdb> proc 0x<address_of_thread_structure>
>     gdb> back
>     Here is a handy GDB macro procedure to generate a 'ps', put it in
>     your ~/.gdbinit file.
[gdb script]

Thanks, this works for me.

More information about the Commits mailing list