From 1b9e1ac4fa0c4c2735150947d5b16e9c11607cc0 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Tue, 14 Oct 2008 17:43:35 +0200 Subject: GDB: non-stop mode. --- hurd/open_issues/gdb_non-stop_mode.mdwn | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 hurd/open_issues/gdb_non-stop_mode.mdwn (limited to 'hurd') diff --git a/hurd/open_issues/gdb_non-stop_mode.mdwn b/hurd/open_issues/gdb_non-stop_mode.mdwn new file mode 100644 index 00000000..c302251f --- /dev/null +++ b/hurd/open_issues/gdb_non-stop_mode.mdwn @@ -0,0 +1,21 @@ +[[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 , +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. -- cgit v1.2.3