Bug 493537 - If GDB crashes, Eclipse just exists silently
Summary: If GDB crashes, Eclipse just exists silently
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 8.8.1   Edit
Hardware: PC Linux
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-12 10:19 EDT by Boian Petkantchin CLA
Modified: 2020-09-04 15:21 EDT (History)
3 users (show)

See Also:

Attachments
CDT Debug View - gdb killed using SIGKILL (16.72 KB, image/png)
2016-05-17 06:17 EDT, Marc Dumais CLA 		no flags Details
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 Boian Petkantchin CLA 2016-05-12 10:19:15 EDT 
I am debugging a C++ program in Eclipse. For some reason, when hitting a breakpoint, the debugging just stops with no message. The Eclipse error log is empty as well.
The correct behavior is to inform the user that GDB has crashed/stopped.

As a workaround, to find out if GDB has crashed, you could attach to the GDB instance that is debugging the application. When the first GDB instance crashes the second will catch the signal. Another option is to enable core dump.
Comment 1 Marc Dumais CLA 2016-05-17 06:17:09 EDT 
Created attachment 261782 [details]
CDT Debug View - gdb killed using SIGKILL
Comment 2 Marc Dumais CLA 2016-05-17 06:19:01 EDT 
Hi,

I have attempted to reproduce this, by using a kill command on the gdb used by cdt. I took a screenshot of the DV and attached it to this bug. Can you confirm if this is similar to what you see?