diff options
Diffstat (limited to 'hurd/open_issues/gdb_non-stop_mode.mdwn')
| -rw-r--r-- | hurd/open_issues/gdb_non-stop_mode.mdwn | 21 |
1 files changed, 0 insertions, 21 deletions
diff --git a/hurd/open_issues/gdb_non-stop_mode.mdwn b/hurd/open_issues/gdb_non-stop_mode.mdwn deleted file mode 100644 index 199cb7ae..00000000 --- a/hurd/open_issues/gdb_non-stop_mode.mdwn +++ /dev/null @@ -1,21 +0,0 @@ -[[!meta copyright="Copyright © 2008 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]]."]]"""]] - -GNU GDB's `gnu-nat.c` doesn't support *non-stop* mode. - -Also, from <http://lists.gnu.org/archive/html/bug-hurd/2008-10/msg00045.html>, -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. |