Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <200510310653.49726.andrew@walrond.org> (raw)
In-Reply-To: <20051028231509.GB9909@nevyn.them.org>

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


  reply	other threads:[~2005-10-31  6:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28 22:30 Andrew Walrond
2005-10-28 23:15 ` Daniel Jacobowitz
2005-10-31  6:53   ` Andrew Walrond [this message]
2005-10-31  9:43     ` Andreas Schwab
2005-10-31 10:03       ` Andrew Walrond
2005-10-31 14:18         ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200510310653.49726.andrew@walrond.org \
    --to=andrew@walrond.org \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox