mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-08-15 12:15:47 +02:00
Bug 339456: Thread created event with wrong id after restart for GDB < 7.0
This commit is contained in:
parent
f83c63c05f
commit
323cc9f222
1 changed files with 11 additions and 0 deletions
|
@ -129,6 +129,17 @@ public class CLIEventProcessor
|
|||
}
|
||||
}
|
||||
|
||||
// Look for an event that indicates a start/restart. This will tell use
|
||||
// we should reset our thread number counter
|
||||
// The printout that seems to occur on restarts (and start) is
|
||||
// [Thread debugging using libthread_db enabled]
|
||||
// Bug 339456
|
||||
pattern = Pattern.compile("^\\[Thread debugging using "); //$NON-NLS-1$
|
||||
matcher = pattern.matcher(exec.getCString());
|
||||
if (matcher.find()) {
|
||||
fLastThreadId = 0;
|
||||
}
|
||||
|
||||
// For GDB thread exit events, we won't use the events generated by GDB. This event is
|
||||
// raised in GDBRunControl class by polling and comparing the ExecutionContexts returned by
|
||||
// -thread-list-ids command. This is done as threads reported by exit event are still reported till
|
||||
|
|
Loading…
Add table
Reference in a new issue