Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335235 - [tracepoint] Deadlock when pressing trace var button in Trace Control view when GDB is running
Summary: [tracepoint] Deadlock when pressing trace var button in Trace Control view wh...
Status: RESOLVED FIXED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 8.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 8.0   Edit
Assignee: Marc Khouzam CLA
QA Contact: Marc Khouzam CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-24 14:11 EST by Marc Khouzam CLA
Modified: 2011-05-18 14:23 EDT (History)
2 users (show)

See Also:

Attachments
Adding timeout to the query to avoid deadlock (5.66 KB, patch)
2011-05-18 14:08 EDT, Marc Khouzam CLA 		marc.khouzam: iplog-
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Khouzam CLA 2011-01-24 14:11:07 EST 
I've used Query in different places for the TraceControl view but I haven't put a timeout.  This causes a deadlock if the view has to query GDB but GDB is running.
Comment 1 Marc Khouzam CLA 2011-05-18 14:08:20 EDT 
Created attachment 196028 [details]
Adding timeout to the query to avoid deadlock


Bug 346217 addresses being able to do tracing operations even while the target is running in all-stop mode.  Until then though, we should not deadlock.

This patch adds a timeout to the query, and prints an error message in the dialog to indicate that we failed to get the trace variables.  In that case, we also do not allow to create new variables.
Comment 2 Marc Khouzam CLA 2011-05-18 14:08:57 EDT 
Committed to HEAD.