This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: cygwin 1.3.3 announcment -- extra words solicited


Christopher Faylor wrote:

> On Tue, Sep 04, 2001 at 10:21:35PM -0400, Charles Wilson wrote:
>>Okay, after making a little batch file and pointing error_start at that, 
>>I can get gdb -nw to start up with state information.
>>
>>First, I get many many many "Program received signal SIGSEGV, 
>>Segmentation fault." messages.  Eventually, I just hit q<RET> to get 
>>past those messages.
>>
> 
> Yes, this is standard.  It was the best way I could find to have gdb
> point at useful info when it attaches to the target.  Hitting 'q' is
> the correct response.


Well, at least I can make a few correct decisions...when they're 
obvious. :-)


>>
>>...child thread 544.0x2dc
>>
>>
>>#0  0x00410732 in exec_command (argv=0x5, envp=0xa01ca70)
>>   at /usr/src/make/src/job.c:2317
>>#1  0x61081e8a in read () at 
>>/usr/src/cygwin/cygwin/winsup/cygwin/uinfo.cc:284
>>#2  0x0040a5cb in func_shell (o=0xa01cd98 "", argv=0x22d52c,
>>
> 
> I don't understand this.  This backtrace is saying that read() is in
> uinfo.cc at line 284.  That's clearly incorrect.  It sounds like the
> symbol table in cygwin1.dll is screwed up.


Oh good.  When I looked at this bt, I couldn't make any sense of it; but 
I just assumed I was stupid.  I'm glad *that's* not the explanation. 
(my self-assessment may still be true, but at least this backtrace isn't 
proof. :-> )


> 
> Something is calling exec_command with an argv of 5, though.
> That's what is causing this problem.
> 
> Judging by the stack trace, it sounds like the make received a signal and
> then maybe something scribbled on the stack.
> 
> Either that or gdb is confused.
> 
> I can't think of any way to debug this further right now.


I'm sorry to contribute to your depression.  (c.f. earlier message 
"discouraged")

>>(Chris, I've sent in a digest-unsub/regular-subscribe message pair, if 
>>you can approve those quickly we can do this realtime(ish).)
>>
> 
> I never saw the subscribe message.  Did you respond to the confirmation?
> Anyway, I just went ahead and subscribed you manually.


The emails crossed.  I got a phone call and was "away from my email" for 
a half hour or so.  Just when I wanted to go "real time". :~&

--Chuck


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]