From 6b366a25f9fd496777ff42932685924eb83696fc Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Wed, 24 Apr 2013 11:46:58 +0200 Subject: IRC. --- open_issues/gdb_attach.mdwn | 29 ++++++++++++++++++++++++++++- 1 file changed, 28 insertions(+), 1 deletion(-) (limited to 'open_issues/gdb_attach.mdwn') diff --git a/open_issues/gdb_attach.mdwn b/open_issues/gdb_attach.mdwn index 8f1b7b48..b9114b69 100644 --- a/open_issues/gdb_attach.mdwn +++ b/open_issues/gdb_attach.mdwn @@ -1,4 +1,4 @@ -[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2012, 2013 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -54,3 +54,30 @@ License|/fdl]]."]]"""]] process That is supposed to work. If the permission match. + + +# `gdb --pid [PID]` + +That is, not explicitly specifying an `executable-file`. + + +## IRC, OFTC, debian-hurd, 2013-04-15 + + I don't seem to be able to run gdb + that happened on the buildd and happens on exodar too + #0 0x010c07cc in ?? () + #1 0x010c1078 in ?? () + #2 0x0109eabf in ?? () + [...] + Backtrace stopped: previous frame inner to this frame (corrupt + stack?) + that's pid 24235 on exodar + I did gdb -p 24235 and then bt + just the output above + I don't know about gdb -p + I usually run gdb + /home/paravoid/gdnsd-1.8.1/plugins/meta/libgdmaps/t/.libs/lt-t17_extn_empty.bin + 24235 + okay, that indeed works + I guess the support for finding out the binary automatically wasn't + done yet on hurd -- cgit v1.2.3