public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug win32/15716] Continuos false SEGMENTATION FAULTS debugging win32 application Date: Thu, 04 Jul 2013 09:59:00 -0000 [thread overview] Message-ID: <bug-15716-4717-rcA1TxtOf8@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15716-4717@http.sourceware.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.
next prev parent reply other threads:[~2013-07-04 9:59 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-03 7:45 [Bug win32/15716] New: " velteyn at gmail dot com 2013-07-03 7:48 ` [Bug win32/15716] " velteyn at gmail dot com 2013-07-03 10:45 ` palves at redhat dot com 2013-07-03 11:28 ` velteyn at gmail dot com 2013-07-03 11:37 ` palves at redhat dot com 2013-07-03 12:16 ` velteyn at gmail dot com 2013-07-04 9:55 ` velteyn at gmail dot com 2013-07-04 9:59 ` palves at redhat dot com [this message] 2013-07-10 13:54 ` velteyn at gmail dot com 2013-07-24 16:11 ` palves at redhat dot com 2013-07-25 7:13 ` velteyn at gmail dot com 2013-07-25 11:03 ` palves at redhat dot com 2021-10-29 7:43 ` loonyivy at gmail dot com 2021-10-29 8:21 ` velteyn at gmail dot com 2023-02-11 17:52 ` tromey at sourceware dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-15716-4717-rcA1TxtOf8@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).