This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug c++/17970] cannot call any function or method with "print" or "call" after command "handle SIGSEGV noprint pass"
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 15 Jun 2015 08:56:05 +0000
- Subject: [Bug c++/17970] cannot call any function or method with "print" or "call" after command "handle SIGSEGV noprint pass"
- Auto-submitted: auto-generated
- References: <bug-17970-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17970
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #14 from Pedro Alves <palves at redhat dot com> ---
Thanks.
It's clear from the logs now:
LLW: waitpid 19430 received Segmentation fault (stopped)
LLW: PTRACE_CONT process 19430, Segmentation fault (preempt 'handle')
LNW: waitpid(-1, ...) returned 0, No child processes
This has already been fixed in master (soon to be 7.10), with:
~~~
commit c9587f88230e9df836f17c195181aaf50c3a1117
Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Date: Thu Feb 12 14:55:08 2015 -0500
Fix non executable stack handling when calling functions in the inferior.
When gdb creates a dummy frame to execute a function in the inferior,
the process may generate a SIGSEGV, SIGTRAP or SIGILL because the stack
is non executable. If the signal handler set in gdb has option print
or stop enabled for these signals gdb handles this correctly.
However, in the case of noprint and nostop the signal is short-circuited
and the inferior process is sent the signal directly. This causes the
inferior to crash because of gdb.
(...)
~~~
*** This bug has been marked as a duplicate of bug 16812 ***
--
You are receiving this mail because:
You are on the CC list for the bug.