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 c++/17970] cannot call any function or method with "print" or "call" after command "handle SIGSEGV noprint pass" Date: Sat, 13 Jun 2015 11:04:00 -0000 [thread overview] Message-ID: <bug-17970-4717-kGae77PP9f@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17970-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17970 --- Comment #12 from Pedro Alves <palves at redhat dot com> --- I mean, it results in a SIGSEGV that GDB internally translates to a SIGTRAP. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-06-13 11:04 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-13 15:51 [Bug c++/17970] New: cannot call any function or method with "print" or "call" Claude at renegat dot net 2015-02-13 18:09 ` [Bug c++/17970] " keiths at redhat dot com 2015-02-13 18:18 ` Claude at renegat dot net 2015-02-13 19:09 ` keiths at redhat dot com 2015-02-13 19:16 ` Claude at renegat dot net 2015-02-13 19:40 ` keiths at redhat dot com 2015-02-14 10:09 ` Claude at renegat dot net 2015-02-14 10:09 ` [Bug c++/17970] cannot call any function or method with "print" or "call" ahter command "handle SIGSEGV noprint pass" Claude at renegat dot net 2015-02-14 20:16 ` [Bug c++/17970] cannot call any function or method with "print" or "call" after " Claude at renegat dot net 2015-02-15 23:33 ` Claude at renegat dot net 2015-06-12 8:30 ` arigo at tunes dot org 2015-06-12 10:19 ` palves at redhat dot com 2015-06-12 19:37 ` arigo at tunes dot org 2015-06-13 10:33 ` palves at redhat dot com 2015-06-13 11:00 ` palves at redhat dot com 2015-06-13 11:04 ` palves at redhat dot com [this message] 2015-06-14 12:41 ` arigo at tunes dot org 2015-06-15 8:56 ` palves at redhat dot com 2015-06-15 21:30 ` dje at google dot com 2015-06-16 8:58 ` palves at redhat dot com
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-17970-4717-kGae77PP9f@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).