This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug breakpoints/16812] SIGSEGV running program after using dprintf-style call and -dprintf-insert


https://sourceware.org/bugzilla/show_bug.cgi?id=16812

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Antoine Tremblay <hexa@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=c9587f88230e9df836f17c195181aaf50c3a1117

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 patch adds a check for SIGSEGV, SIGTRAP or SIGILL so that these
    signals are sent to gdb rather than short-circuited in the inferior.
    gdb then handles them properly and the inferior process does not
    crash.

    This patch also fixes the same behavior in gdbserver.

    Also added a small testcase to test the issue called
catch-gdb-caused-signals.

    This applies to Linux only, tested on Linux.

    gdb/ChangeLog:
        PR breakpoints/16812
        * linux-nat.c (linux_nat_filter_event): Report SIGTRAP,SIGILL,SIGSEGV.
        * nat/linux-ptrace.c (linux_wstatus_maybe_breakpoint): Add.
        * nat/linux-ptrace.h: Add linux_wstatus_maybe_breakpoint.

    gdb/gdbserver/ChangeLog:
        PR breakpoints/16812
        * linux-low.c (wstatus_maybe_breakpoint): Remove.
        (linux_low_filter_event): Update wstatus_maybe_breakpoint name.
        (linux_wait_1): Report SIGTRAP,SIGILL,SIGSEGV.

    gdb/testsuite/ChangeLog:
        PR breakpoints/16812
        * gdb.base/catch-gdb-caused-signals.c: New file.
        * gdb.base/catch-gdb-caused-signals.exp: New file.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]