gdb drops out with 'I/O possible message'

[Andrew Walrond]

On Saturday 29 October 2005 00:15, Daniel Jacobowitz wrote:
> On Fri, Oct 28, 2005 at 11:30:00PM +0100, Andrew Walrond wrote:
> > What might cause gdb to do this?
>
> I have no idea.  That message comes from ruby rather than GDB.

No, it doesn't...

$ grep -rF 'I/O possible' gdb-6.3
gdb-6.3/libiberty/strsignal.c:  ENTRY(SIGIO, "SIGIO", "I/O possible"),
gdb-6.3/gdb/proc-events.c:  { SIGIO, "SIGIO", "Socket I/O possible" },  /* 
alias for SIGPOLL */
gdb-6.3/gdb/signals/signals.c:  {"SIGIO", "I/O possible"},
andrew@orac test $

I have seen gdb drop out with this message when debugging c, c++ as well as 
ruby projects, but not frequently. In this particular example, I immediately 
re-ran gdb with the same commands and it worked exactly as expected.

I don't see 'I/O possible' often, but when I do gdb always seems to just exit.

This is running on linux x86_64 64bit linux with recent (-branch) glibc+nptl

Andrew Walrond