-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
gdb: add Python events for program space addition and removal
Initially I just wanted a Python event for when GDB removes a program space, I'm writing a Python extension that caches information for each program space, and need to know when I should discard entries for a particular program space. But, it seemed easy enough to also add an event for when GDB adds a new program space, so I went ahead and added both new events. Of course, we don't currently have an observable for program space addition or removal, so I first needed to add these. After that it's pretty simple to add two new Python events and have these trigger. The two new event registries are: events.new_progspace events.free_progspace These emit NewProgspaceEvent and FreeProgspaceEvent objects respectively, each of these new event types has a 'progspace' attribute that contains the relevant gdb.Progspace object. There's a couple of things to be mindful of. First, it is not possible to catch the NewProgspaceEvent for the very first program space, the one that is created when GDB first starts, as this program space is created before any Python scripts are sourced. In order to allow this event to be caught we would need to defer creating the first program space, and as a consequence the first inferior, until some later time. But, existing scripts could easily depend on there being an initial inferior, so I really don't think we should change that -- and so, we end up with the consequence that we can't catch the event for the first program space. The second, I think minor, issue, is that GDB doesn't clean up its program spaces upon exit -- or at least, they are not cleaned up before Python is shut down. As a result, any program spaces in use at the time GDB exits don't generate a FreeProgspaceEvent. I'm not particularly worried about this for my use case, I'm using the event to ensure that a cache doesn't hold stale entries within a single GDB session. It's also easy enough to add a Python at-exit callback which can do any final cleanup if needed. Finally, when testing, I did hit a slightly weird issue with some of the remote boards (e.g. remote-stdio-gdbserver). As a consequence of this issue I see some output like this in the gdb.log: (gdb) PASS: gdb.python/py-progspace-events.exp: inferior 1 step FreeProgspaceEvent: <gdb.Progspace object at 0x7fb7e1d19c10> warning: cannot close "target:/lib64/libm.so.6": Cannot execute this command while the target is running. Use the "interrupt" command to stop the target and then try again. warning: cannot close "target:/lib64/libc.so.6": Cannot execute this command while the target is running. Use the "interrupt" command to stop the target and then try again. warning: cannot close "target:/lib64/ld-linux-x86-64.so.2": Cannot execute this command while the target is running. Use the "interrupt" command to stop the target and then try again. do_parent_stuff () at py-progspace-events.c:41 41 ++global_var; (gdb) PASS: gdb.python/py-progspace-events.exp: step The 'FreeProgspaceEvent ...' line is expected, that's my test Python extension logging the event. What isn't expected are all the blocks like: warning: cannot close "target:/lib64/libm.so.6": Cannot execute this command while the target is running. Use the "interrupt" command to stop the target and then try again. It turns out that this has nothing to do with my changes, this is just a consequence of reading files over the remote protocol. The test forks a child process which GDB stays attached too. When the child exits, GDB cleans up by calling prune_inferiors, which in turn can result in GDB trying to close some files that are open because of the inferior being deleted. If the prune_inferiors call occurs when the remote target is running (and in non-async mode) then GDB will try to send a fileio packet while the remote target is waiting for a stop reply, and the remote target will throw an error, see remote_target::putpkt_binary in remote.c for details. I'm going to look at fixing this, but, as I said, this is nothing to do with this change, I just mention it because I ended up needing to account for these warning messages in one of my tests, and it all looks a bit weird. Approved-By: Tom Tromey <[email protected]> Reviewed-By: Eli Zaretskii <[email protected]>
- Loading branch information
Showing
11 changed files
with
349 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,73 @@ | ||
/* This testcase is part of GDB, the GNU debugger. | ||
Copyright 2023 Free Software Foundation, Inc. | ||
This program is free software; you can redistribute it and/or modify | ||
it under the terms of the GNU General Public License as published by | ||
the Free Software Foundation; either version 3 of the License, or | ||
(at your option) any later version. | ||
This program is distributed in the hope that it will be useful, | ||
but WITHOUT ANY WARRANTY; without even the implied warranty of | ||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the | ||
GNU General Public License for more details. | ||
You should have received a copy of the GNU General Public License | ||
along with this program. If not, see <http://www.gnu.org/licenses/>. */ | ||
|
||
#include <unistd.h> | ||
#include <sys/types.h> | ||
#include <assert.h> | ||
#include <sys/wait.h> | ||
|
||
/* This gives the inferior something to do. */ | ||
volatile int global_var = 0; | ||
|
||
void | ||
breakpt () | ||
{ /* Nothing. */ } | ||
|
||
void | ||
do_child_stuff () | ||
{ | ||
breakpt (); | ||
++global_var; | ||
} | ||
|
||
void | ||
do_parent_stuff () | ||
{ | ||
breakpt (); | ||
++global_var; | ||
} | ||
|
||
void | ||
create_child () | ||
{ | ||
int stat; | ||
pid_t wpid; | ||
breakpt (); | ||
pid_t pid = fork (); | ||
assert (pid != -1); | ||
|
||
if (pid == 0) | ||
{ | ||
/* Child. */ | ||
do_child_stuff (); | ||
return; | ||
} | ||
|
||
/* Parent. */ | ||
do_parent_stuff (); | ||
wpid = waitpid (pid, &stat, 0); | ||
assert (wpid == pid); | ||
} | ||
|
||
|
||
|
||
int | ||
main () | ||
{ | ||
create_child (); | ||
return 0; | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,125 @@ | ||
# Copyright (C) 2023 Free Software Foundation, Inc. | ||
|
||
# This program is free software; you can redistribute it and/or modify | ||
# it under the terms of the GNU General Public License as published by | ||
# the Free Software Foundation; either version 3 of the License, or | ||
# (at your option) any later version. | ||
# | ||
# This program is distributed in the hope that it will be useful, | ||
# but WITHOUT ANY WARRANTY; without even the implied warranty of | ||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the | ||
# GNU General Public License for more details. | ||
# | ||
# You should have received a copy of the GNU General Public License | ||
# along with this program. If not, see <http://www.gnu.org/licenses/>. | ||
|
||
# This file is part of the GDB testsuite. It tests the program space | ||
# related events in the Python API. | ||
|
||
load_lib gdb-python.exp | ||
|
||
require allow_python_tests | ||
|
||
standard_testfile | ||
|
||
if {[prepare_for_testing "preparing" $testfile $srcfile] == -1} { | ||
return -1 | ||
} | ||
|
||
set pyfile [gdb_remote_download host ${srcdir}/${subdir}/py-progspace-events.py] | ||
gdb_test_no_output "source ${pyfile}" "load python file" | ||
|
||
if {![runto_main]} { | ||
return | ||
} | ||
|
||
gdb_breakpoint breakpt | ||
|
||
gdb_continue_to_breakpoint "run to breakpt function" | ||
|
||
gdb_test_no_output "set detach-on-fork off" | ||
|
||
# Continue until the parent process forks and a new child is added. | ||
# Done this way so we can count the new progspace events; we expect to | ||
# see exactly one. | ||
set new_progspace_event_count 0 | ||
gdb_test_multiple "continue" "continue until child process appears" { | ||
-re "^NewProgspaceEvent: <gdb.Progspace object at $hex>\r\n" { | ||
# This is a correctly formed event line. | ||
incr new_progspace_event_count | ||
exp_continue | ||
} | ||
|
||
-re "^NewProgspaceEvent:\[^\r\n\]+\r\n" { | ||
# This is an incorrectly formed event line. | ||
fail $gdb_test_name | ||
} | ||
|
||
-re "^$gdb_prompt $" { | ||
pass $gdb_test_name | ||
} | ||
|
||
-re "^\[^\r\n\]*\r\n" { | ||
exp_continue | ||
} | ||
} | ||
|
||
gdb_assert { $new_progspace_event_count == 1 } \ | ||
"only a single new progspace event seen" | ||
|
||
# Switch to inferior 2 and continue until we hit breakpt. | ||
gdb_test "inferior 2" "\\\[Switching to inferior 2 .*" | ||
gdb_continue_to_breakpoint "run to breakpt in inferior 2" | ||
|
||
# Let inferior 2 exit. The new program space is not removed at this | ||
# point. | ||
gdb_test "continue" \ | ||
[multi_line \ | ||
"^Continuing\\." \ | ||
"\\\[Inferior $decimal \[^\r\n\]+ exited normally\\\]"] \ | ||
"continue until inferior 2 exits" | ||
|
||
gdb_test "inferior 1" "\\\[Switching to inferior 1 .*" | ||
|
||
# Step the inferior. During this process GDB will prune the now | ||
# defunct inferior, which deletes its program space, which should | ||
# trigger the FreeProgspaceEvent. | ||
# | ||
# However, there is a slight problem. When the target is remote, and | ||
# GDB is accessing files using remote fileio, then GDB will attempt to | ||
# prune the inferior at a point in time when the remote target is | ||
# waiting for a stop reply. Pruning an inferior causes GDB to close | ||
# files associated with that inferior. | ||
# | ||
# In non-async mode we can't send fileio packets while waiting for a | ||
# stop reply, so the attempts to close files fails, and this shows up | ||
# as an error. | ||
# | ||
# As this error has nothing to do with the feature being tested here, | ||
# we just accept the error message, the important part is the | ||
# 'FreeProgspaceEvent' string, so long as that appears (just once) | ||
# then the test is a success. | ||
set warning_msg \ | ||
[multi_line \ | ||
"warning: cannot close \"\[^\r\n\]+\": Cannot execute this command while the target is running\\." \ | ||
"Use the \"interrupt\" command to stop the target" \ | ||
"and then try again\\."] | ||
|
||
gdb_test "step" \ | ||
[multi_line \ | ||
"^FreeProgspaceEvent: <gdb.Progspace object at $hex>(?:\r\n$warning_msg)*" \ | ||
"do_parent_stuff \\(\\) at \[^\r\n\]+" \ | ||
"$decimal\\s+\[^\r\n\]+"] | ||
|
||
# Let this inferior run to completion. | ||
gdb_continue_to_end | ||
|
||
# Check the program space events trigger when a new inferior is | ||
# manually added and removed. | ||
gdb_test "add-inferior" \ | ||
[multi_line \ | ||
"^NewProgspaceEvent: <gdb.Progspace object at $hex>" \ | ||
"\\\[New inferior 3\\\]" \ | ||
"Added inferior 3\[^\r\n\]*"] | ||
gdb_test "remove-inferior 3" \ | ||
"^FreeProgspaceEvent: <gdb.Progspace object at $hex>" |
Oops, something went wrong.