From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-22921-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 12310 invoked by alias); 31 Oct 2005 06:53:55 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Received: (qmail 12300 invoked by uid 22791); 31 Oct 2005 06:53:53 -0000
Received: from host62-24-231-115.dsl.vispa.com (HELO orac.walrond.org) (62.24.231.115)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 31 Oct 2005 06:53:53 +0000
Received: from localhost ([127.0.0.1])
	by orac.walrond.org with esmtp (Exim 4.51)
	id 1EWTYD-0002jC-WA
	for gdb@sources.redhat.com; Mon, 31 Oct 2005 06:53:50 +0000
From: Andrew Walrond <andrew@walrond.org>
To: gdb@sources.redhat.com
Subject: Re: gdb drops out with 'I/O possible message'
Date: Mon, 31 Oct 2005 06:53:00 -0000
User-Agent: KMail/1.8.2
References: <200510282330.00638.andrew@walrond.org> <20051028231509.GB9909@nevyn.them.org>
In-Reply-To: <20051028231509.GB9909@nevyn.them.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200510310653.49726.andrew@walrond.org>
X-SW-Source: 2005-10/txt/msg00226.txt.bz2

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