seer
seer copied to clipboard
epasveer
Not all apps deal with threads.
Dave Marples [email protected] wrote:
Thread Info may not always be useful in the embedded environment. It can be as some of the debug stubs (e.g. openocd) present the target OS threads via gdb, but it should be toggle-able. In general, do you intend to make the windows configurable?
To be honest, I wasn't planning to. Is it that much of a problem? Do others feel the same way?
Just auto-hide the threads tab or whatever if only 1 is enumerated at the start, can always reveal it permanently when more than one is enumerated later during the debugging session
I just realized the "splitter" handle:
can be dragged downwards. If dragged far enough, the Thread Info will be hidden.
Seer will remember this. The next time Seer is started, it will still be hidden.
Dragging the "splitter" upwards will bring it back.
I'm going to close this task. I'm thinking I will keep the thread view. I've added other features to the same view (vfork handling and Ada tasks).