summaryrefslogtreecommitdiff
path: root/open_issues/gdb_non-stop_mode.mdwn
diff options
context:
space:
mode:
authorhttps://me.yahoo.com/a/g3Ccalpj0NhN566pHbUl6i9QF0QEkrhlfPM-#b1c14 <diana@web>2015-02-16 20:08:03 +0100
committerGNU Hurd web pages engine <web-hurd@gnu.org>2015-02-16 20:08:03 +0100
commit95878586ec7611791f4001a4ee17abf943fae3c1 (patch)
tree847cf658ab3c3208a296202194b16a6550b243cf /open_issues/gdb_non-stop_mode.mdwn
parent8063426bf7848411b0ef3626d57be8cb4826715e (diff)
rename open_issues.mdwn to service_solahart_jakarta_selatan__082122541663.mdwn
Diffstat (limited to 'open_issues/gdb_non-stop_mode.mdwn')
-rw-r--r--open_issues/gdb_non-stop_mode.mdwn26
1 files changed, 0 insertions, 26 deletions
diff --git a/open_issues/gdb_non-stop_mode.mdwn b/open_issues/gdb_non-stop_mode.mdwn
deleted file mode 100644
index adaff102..00000000
--- a/open_issues/gdb_non-stop_mode.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-[[!meta copyright="Copyright © 2008, 2009, 2014 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
-document under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no Invariant
-Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
-is included in the section entitled [[GNU Free Documentation
-License|/fdl]]."]]"""]]
-
-[[!meta title="GDB's non-stop mode"]]
-
-[[!tag open_issue_gdb]]
-
-GNU GDB's `gnu-nat.c` doesn't support *non-stop* mode.
-
-Also, from [[!message-id "200810131935.35253.pedro@codesourcery.com"]],
-GNU GDB's Pedro Alves:
-
-> I also notice that when going through the shell in non-stop mode, it would be
-> more correct to resume all threads --- we don't want non-stop and its
-> scheduler-locking to apply to the shell. Basically, non-stop should be off
-> if there are pending execs. This was an existing issue, and doesn't affect
-> linux today, so I'll just ignore that for now, as it needs more tweaking to
-> fix.