This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: gdb/2241: Different errno when program signalled from gdb
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 26 Mar 2007 17:38:01 -0000
- Subject: Re: gdb/2241: Different errno when program signalled from gdb
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR gdb/2241; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: chris.auston@crsoftwareinc.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/2241: Different errno when program signalled from gdb
Date: Mon, 26 Mar 2007 13:33:07 -0400
On Mon, Mar 26, 2007 at 04:31:44PM -0000, chris.auston@crsoftwareinc.com wrote:
> Program received signal SIGINT, Interrupt.
> [Switching to Thread -1208489328 (LWP 22061)]
> 0x00d958d2 in _dl_sysinfo_int80 () at rtld.c:576
> 576 relocate_doit (void *a)
> Current language: auto; currently c
> (gdb) sig 2
> Continuing with signal SIGINT.
> errno=514
>
> Program exited normally.
> (gdb)
FYI, I can reproduce this. 514 is ERESTARTNOHAND, a Linux internal
errno code used for interrupted syscalls. We've manually interrupted
the syscall.
I'm not entirely sure if this should be considered a GDB or kernel
bug... someone will have to consider how the two should work together.
It seems like the syscall should have been restarted.
--
Daniel Jacobowitz
CodeSourcery