Bug 8903 - java GC generates SIGSEGV
Summary: java GC generates SIGSEGV
Status: RESOLVED DUPLICATE of bug 7221
Alias: None
Product: gdb
Classification: Unclassified
Component: java (show other bugs)
Version: 5.0
: P3 enhancement
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-26 18:18 UTC by gbs
Modified: 2009-08-04 21:09 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gbs 2004-10-26 18:18:02 UTC
[Converted from Gnats 1798]

Problem occurs while using gdb to debug C/C++ programs with embedded Sun JVM. 

The JVM can generate SIGSEGV's as part of it's normal garbage collection. The JVM traps and handles these signals. 

However, gdb terminates the program C/C++ program.

Is there some way gdb could ignore the SIGSEGV's from the JVM, while continuing to process other SIGSEGV's in it's normal way?

Release:
5.0 plus

Environment:
Solaris, Cygwin, Windows
Comment 1 Tom Tromey 2009-08-04 21:09:37 UTC
I think this could probably be done if there were a way to
attach commands to a "signal breakpoint".
However, AFAIK there is no way to do this.
I'm closing this as a duplicate of the feature request for "catch signal".


*** This bug has been marked as a duplicate of 7221 ***