This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
gdb/2559: [regression] stop hooks run after printing stack frame
- From: vargaz at gmail dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 26 Nov 2008 02:21:52 -0000
- Subject: gdb/2559: [regression] stop hooks run after printing stack frame
- Reply-to: vargaz at gmail dot com
>Number: 2559
>Category: gdb
>Synopsis: [regression] stop hooks run after printing stack frame
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Wed Nov 26 02:28:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: vargaz@gmail.com
>Release: GNU gdb (GDB) 6.8.50.20081126-cvs
>Organization:
>Environment:
debian unstable amd64
>Description:
According to the gdb manual, stop hooks were executed before
the stack frame information was printed when the program
was stopped. This got broken by this patch:
http://sourceware.org/ml/gdb-patches/2008-09/msg00193.html
Running the hook code before printing the stack frame is
useful for things like debugging JITted code, i.e. the hook
could load symbol information for the JITted code using
add-symbol-file.
>How-To-Repeat:
define hook-stop
echo "Hello."
end
break main
run
In gdb 6.8, the "Hello" message was printed before the stack
frame, in the cvs version, it is printed after.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: