This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug win32/14685] New: semantic error found in windows-nat.c:986causes permanant hang for debuggee process
- From: "jojelino at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 08 Oct 2012 20:55:43 +0000
- Subject: [Bug win32/14685] New: semantic error found in windows-nat.c:986causes permanant hang for debuggee process
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=14685
Bug #: 14685
Summary: semantic error found in windows-nat.c:986 causes
permanant hang for debuggee process
Product: gdb
Version: HEAD
Status: NEW
Severity: critical
Priority: P2
Component: win32
AssignedTo: unassigned@sourceware.org
ReportedBy: jojelino@gmail.com
Classification: Unclassified
Created attachment 6673
--> http://sourceware.org/bugzilla/attachment.cgi?id=6673
proposed patch
http://sourceware.org/git/?p=gdb.git;a=commit;f=gdb/windows-nat.c;h=8094fa2e73f05bd42a7005fd005aeaa26ea20c26
In this commit, handle_output_debug_string modifies dwThreadId of
current_event. and there is no way to figure out which thread actually sent the
debug event after that. it would be possible unless dwThreadId hasn't modified.
In the result, there isn't any ContinueDebugEvent call for the thread that sent
the debug event to the debugger. make the debuggee hang.
So, I propose the patch which fixes the problem. please review it.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.