This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
c++/2206: Checkpointing SIGINT on restart
- From: uri at 4refs dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 4 Dec 2006 16:24:13 -0000
- Subject: c++/2206: Checkpointing SIGINT on restart
- Reply-to: uri at 4refs dot com
>Number: 2206
>Category: c++
>Synopsis: Checkpointing SIGINT on restart
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Dec 04 16:28:01 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: uri@4refs.com
>Release: gdb-6.5
>Organization:
>Environment:
os=Redhat Enterprise 4
arch=x86_64
>Description:
Sometimes when restarting checkpoints a SIGINT is received. Usually one can just finish the call stack or continue.
(gdb) restart 1
Program received signal SIGINT, Interrupt.
0x00000036b160f6f0 in lseek64 () from /lib64/ld-linux-x86-64.so.2
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on"
Evaluation of the expression containing the function (lseek64) will be abandoned.
>How-To-Repeat:
Unknown
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: