public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "deCarmo, Linden" <LDecarmo@convergentnet.com>
To: "'insight@sourceware.cygnus.com'" <insight@sourceware.cygnus.com>
Subject: FW: Interrupted system call problem
Date: Tue, 03 Apr 2001 05:30:00 -0000	[thread overview]
Message-ID: <33890A53976FD41191A800B0D03DF196953D9E@gator.techcontrol.com> (raw)

Just noticed that I forgot to copy the list on my response.

Any ideas to work around this?

> On Tue, 20 Mar 2001, deCarmo, Linden wrote:
> 
> > Ok, the latest snapshot hangs rather than reports 
> "Interrupted system call"
> > whenever the the code below is executed.  To be specific, the source
> > disappears and it reports:
> > 
> > Select function name to disassemble
> > 
> > ====
> > 
> > The stack is listed as ???? 
> 
> You're probably in a dynamic loader stub or similar, sitting 
> at the first 
> instruction. Gdb is obviously a little confused about where it is... 
> (This should not happen.)
> 
> > struct timeval tv;
> >  	336	
> > -	337		tv.tv_sec = seconds;
> >  	338		tv.tv_usec = microseconds;
> > -	340		return(select(0,NULL,NULL,NULL,&tv));
> 
> Let me guess, it does this on line 340? Then I would guess 
> that shared 
> libraries are a little broken on your system. Hmmm.... 
> Solaris 2.8...  
>

Works fine with ddd/gdb, and gdb -nw.
 
> > Any idea what I can try next?  Its weird that ddd doesn't 
> have the same
> > issue using gdb.
> 
> Does command line gdb exhibit the same behavior (run the insight gdb 
> with the "-nw" flag)?
> 

No, works ok with -nw.  Only Insight exhibits this behavior.
 

             reply	other threads:[~2001-04-03  5:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-03  5:30 deCarmo, Linden [this message]
2001-04-12  9:51 deCarmo, Linden
2001-04-13 14:59 ` Keith Seitz
2001-04-16 14:59 deCarmo, Linden

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=33890A53976FD41191A800B0D03DF196953D9E@gator.techcontrol.com \
    --to=ldecarmo@convergentnet.com \
    --cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).