Joshua,
There does seem to be an issue with the way the debugger is handling segfaults in the application. I'm not sure why, since the segfault should be treated like any other suspend event (such as hitting a breakpoint). There must be something different in the way gdb handles these. I spent some time trying to track down the problem without luck.
I'm not going to be able to get to look at it again for a couple of weeks now, but I've opened bug #421554 in the mean time. Feel free to add any comments you think might be useful.
Greg
Frequently, when I am running in the debugger, it simply stops
responding to any inputs from the GUI. All expressions now say
"(pending)" and I can no longer pause or stop any processes. I have
to go to the terminal, SSH to the cluster, and manually kill
everything. The problem is especially bad when a segfault or fpe
causes a thread to pause, which is of course the worst time for the
debugger to give me trouble.
Are there known fatal bugs that cause this, is this just a normal
pitfall of parallel debugging, or is there something I need to do
with the cluster?
--
Joshua
Strodtbeck, PhD | Research Engineer
<Screenshot - 07112013 - 10:57:10 AM.png>
O: (608)
831-3811
_______________________________________________ ptp-user mailing list ptp-user@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ptp-user
|