Re: Still 100% usage and weird problems with recent snapshots?

[Glenn Spell <glenn at gs dot fay dot nc dot us>]

On  2 Mar 2000 around  1:13PM (-0500) Chris Faylor wrote:

> Has the recent snapshot solved the problem for everyone else or are
> there still problems?

As I reported earlier, the bash I was using up until recently will
not run with any snapshots after the 99-12-04. The only thing I am
aware of about this bash-2.03 that won't run is that I compiled it
with gcc-2.95 (I have not yet updated gcc from 2.95.)

My work-around in order to use the latest snapshots was to revert
to a bash-2.03 that I compiled with egcs-1.1.1. I'm not suggesting
anything... just reporting observations. I offer this just in case
it may be related to anything else that's going on with the latest
snapshots.

Following is all the info I can come up with since this bash does
not run far enough to get any strace output.

When starting this bash via Insight, the Source Window moves to
the file "shell.c" function "main", at the following line (*):

 	305	  /* Catch early SIGINTs. */
*	306	  code = setjmp (top_level);
-	307	  if (code)
-	308	    exit (2);

-	0x401208	<main>:		    push   %ebp
-	0x401209	<main+1>:	    mov    %ebp,%esp
-	0x40120b	<main+3>:	    sub    %esp,28
-	0x40120e	<main+6>:	    push   %edi
-	0x40120f	<main+7>:	    push   %esi
-	0x401210	<main+8>:	    push   %ebx
-	0x401211	<main+9>:	    call   0x462360 <__main>
*	0x401216	<main+14>:	    mov    %ds:0x46a8b0,0x1
-	0x401220	<main+24>:	    add    %esp,-4
-	0x401223	<main+27>:	    push   0x46a8b4
-	0x401228	<main+32>:	    push   0
-	0x40122a	<main+34>:	    push   0
-	0x40122c	<main+36>:	    call   0x462450 <sigprocmask>
-	0x401231	<main+41>:	    add    %esp,-12
-	0x401234	<main+44>:	    push   0x46a7e0
-	0x401239	<main+49>:	    call   0x462448 <setjmp>
-	0x40123e	<main+54>:	    add    %esp,32
-	0x401241	<main+57>:	    test   %eax,%eax

When I start the program running I immediately get a
segfault and the line number does not change in the Source
Window. Then, the source code disappears and Insight shows
the current function as "size_of_stack_frame" and prints
this lone message in the Insight Source Window:

"Unable to Read Instructions at 0x61041a16"

The Insight Memory Window displays the following:	

                  0            4            8           C
0x61041a16  {0x74107339} {0x0cec8358} {0x5008438d}{0x00bae1e8}

0x74107339       N/A          N/A          N/A         N/A

View Thread List (Processes) lists the following:

2 thread -177397.0xfffc280f  0xbff9638a in _size_of_stack_reserve__ ()
1 thread -177397.0xfffdcfc3  0x61041a16 in _size_of_stack_reserve__ ()

At another invocation, Windows reports the following:

BASH caused an invalid page fault in
module CYGWIN1.DLL at 0157:61041a16.
Registers:
EAX=fffdffab CS=0157 EIP=61041a16 EFLGS=00010282
EBX=00000000 SS=015f ESP=0259fba4 EBP=0259fbbc
ECX=ffffffff DS=015f ESI=fffdffab FS=2007
EDX=ffffffff ES=015f EDI=ffffffff GS=0000
Bytes at CS:EIP:
39 73 10 74 58 83 ec 0c 8d 43 08 50 e8 e1 ba 00

I hope this helps 'cause that's all I know.

-glenn

-- 
  ________________________________________      _       _____
 )                                        )_ _ (__\____o /_/_ |
 )    Glenn Spell <glenn@gs.fay.nc.us>    )     >-----._/_/__]>
 )________________________________________)               `0  |

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com