aboutsummaryrefslogtreecommitdiff
path: root/bfd/elfxx-tilegx.c
diff options
context:
space:
mode:
authorJoel Brobecker <brobecker@gnat.com>2013-05-06 12:41:14 +0000
committerJoel Brobecker <brobecker@gnat.com>2013-05-06 12:41:14 +0000
commit726ce67c26bb6e9525d6d74dae6ff0a166289367 (patch)
treefaac6a47f1e7cade1b91afb033559381d7456f3a /bfd/elfxx-tilegx.c
parentc8c9911faa52bbd1edcae3a12181bb76fa867f31 (diff)
downloadgdb-726ce67c26bb6e9525d6d74dae6ff0a166289367.zip
gdb-726ce67c26bb6e9525d6d74dae6ff0a166289367.tar.gz
gdb-726ce67c26bb6e9525d6d74dae6ff0a166289367.tar.bz2
darwin: warning resuming inferior after attach
This patch avoids a warning when resuming the execution of a program that we attached to. For instance: (gdb) attach 29989 (gdb) continue Continuing. warning: Mach error at "/[...]/darwin-nat.c:738" in function "darwin_resume_thread": (os/kern) failure (0x5) The warning is relatively harmless, but worrisome for the average user. The warning comes from the fact that darwin_wait recorded that the fake stop event corresponding to the suspend action was caused by the main thread being suspended on a SIGTRAP. As a result of this, when resuming the program's execution, we try to resume the thread's execution as well. This is where the issue occurs, as the thread was not in fact suspended, thus triggering the warning. gdb/ChangeLog: * darwin-nat.c (darwin_setup_fake_stop_event): New function. (darwin_attach): Adjust using darwin_setup_fake_stop_event.
Diffstat (limited to 'bfd/elfxx-tilegx.c')
0 files changed, 0 insertions, 0 deletions