This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug win32/15716] Continuos false SEGMENTATION FAULTS debugging win32 application
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 04 Jul 2013 09:59:01 +0000
- Subject: [Bug win32/15716] Continuos false SEGMENTATION FAULTS debugging win32 application
- Auto-submitted: auto-generated
- References: <bug-15716-4717 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15716
--- Comment #7 from Pedro Alves <palves at redhat dot com> ---
(gdb) apropos SIGSEGV
handle -- Specify how to handle a signal
(gdb) help handle
Specify how to handle a signal.
Args are signals and actions to apply to those signals.
Symbolic signals (e.g. SIGSEGV) are recommended but numeric signals
from 1-15 are allowed for compatibility with old versions of GDB.
Numeric ranges may be specified with the form LOW-HIGH (e.g. 1-5).
The special arg "all" is recognized to mean all signals except those
used by the debugger, typically SIGTRAP and SIGINT.
Recognized actions include "stop", "nostop", "print", "noprint",
"pass", "nopass", "ignore", or "noignore".
Stop means reenter debugger if this signal happens (implies print).
Print means print a message if this signal happens.
Pass means let program see this signal; otherwise program doesn't know.
Ignore is a synonym for nopass and noignore is a synonym for pass.
Pass and Stop may be combined.
(gdb) handle SIGSEGV pass nostop
--
You are receiving this mail because:
You are on the CC list for the bug.