Interrupted system call problem

Interrupted system call problem

[deCarmo, Linden]

About a year ago, someone reported that Insight threw an Interrupted system
call error while debugging.  The consensus was that it was likely caused by
mixing GUI/console modes.

Unfortunately, I'm running into the same problem, and I'm not mixing modes.
The problem seems to surface when a select() is done.

If I run the non-GUI gdb (i.e. gdb -nw), or DDD, this problem doesn't occur.

Here's my version info...

GNU gdb 5.0
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.8".

RE: Interrupted system call problem

[Keith Seitz]

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...  

> 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)?

If it also has this problem, then there has been a regression in gdb 
handling shared libraries on Solaris 2.8. Ask on the gdb list 
(gdb@sources.redhat.com). There will be a lot more people over there who 
would know about this.

Good luck.
Keith

RE: Interrupted system call problem

[deCarmo, Linden]

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 ???? 

struct timeval tv;
 	336	
-	337		tv.tv_sec = seconds;
 	338		tv.tv_usec = microseconds;
-	340		return(select(0,NULL,NULL,NULL,&tv));
 	341	

Doesn't really matter what's in tv, but here's a sample

(gdb) display tv
1: tv = {tv_sec = 3, tv_usec = 0}

(gdb) show version
GNU gdb 20010313
Copyright 2001 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.8".

===============

Any idea what I can try next?  Its weird that ddd doesn't have the same
issue using gdb.


> -----Original Message-----
> From: Keith Seitz [ mailto:keiths@cygnus.com ]
> Sent: Monday, March 12, 2001 4:07 PM
> To: deCarmo, Linden
> Cc: 'insight@sourceware.cygnus.com'
> Subject: Re: Interrupted system call problem
> 
> 
> On Mon, 12 Mar 2001, deCarmo, Linden wrote:
> 
> > Haven't seen a reply, so here's a follow-up question:
> > 
> > Should I try a development snapshot version to see if it solves the
> > Interrupted system call issue or is this a previously 
> unreported problem?
> 
> Sorry. I don't know much about this interrupted system call 
> stuff, but, 
> yes, I would encourage you to grab the latest snapshot.
> 
> Unfortunatley for users, the snapshots usually just contain a 
> lot of bug 
> fixes as well as new, experimental features.
> 
> Keith
> 

Re: Interrupted system call problem

[Keith Seitz]

On Mon, 12 Mar 2001, deCarmo, Linden wrote:

> Haven't seen a reply, so here's a follow-up question:
> 
> Should I try a development snapshot version to see if it solves the
> Interrupted system call issue or is this a previously unreported problem?

Sorry. I don't know much about this interrupted system call stuff, but, 
yes, I would encourage you to grab the latest snapshot.

Unfortunatley for users, the snapshots usually just contain a lot of bug 
fixes as well as new, experimental features.

Keith

Re: Interrupted system call problem

[deCarmo, Linden]

Haven't seen a reply, so here's a follow-up question:

Should I try a development snapshot version to see if it solves the
Interrupted system call issue or is this a previously unreported problem?

Linden deCarmo
ldecarmo@convergentnet.com