diff options
| author | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2015-02-18 00:58:35 +0100 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2015-02-18 00:58:35 +0100 |
| commit | 49a086299e047b18280457b654790ef4a2e5abfa (patch) | |
| tree | c2b29e0734d560ce4f58c6945390650b5cac8a1b /open_issues/gdb_non-stop_mode.mdwn | |
| parent | e2b3602ea241cd0f6bc3db88bf055bee459028b6 (diff) | |
| download | web-49a086299e047b18280457b654790ef4a2e5abfa.tar.gz web-49a086299e047b18280457b654790ef4a2e5abfa.tar.bz2 web-49a086299e047b18280457b654790ef4a2e5abfa.zip | |
Revert "rename open_issues.mdwn to service_solahart_jakarta_selatan__082122541663.mdwn"
This reverts commit 95878586ec7611791f4001a4ee17abf943fae3c1.
Diffstat (limited to 'open_issues/gdb_non-stop_mode.mdwn')
| -rw-r--r-- | open_issues/gdb_non-stop_mode.mdwn | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/open_issues/gdb_non-stop_mode.mdwn b/open_issues/gdb_non-stop_mode.mdwn new file mode 100644 index 00000000..adaff102 --- /dev/null +++ b/open_issues/gdb_non-stop_mode.mdwn @@ -0,0 +1,26 @@ +[[!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. |