On 24 May 2006 11:05, [EMAIL PROTECTED] wrote:
> On Wed, May 24, 2006 at 01:49:53AM -0700, Brian Dessent wrote:
>> Sigh. We've been through this ad nauseum in the archives. This is how
>> it's supposed to work, there's nothing wrong here. Gdb doesn't know any
>> better though, and reports it as a SIGSEGV, when it is not. Did you not
>> notice that when you run the program outside of the debugger it does not
>> fault? If you use a recent Cygwin snapshot and a gdb built from CVS you
>> see no such fault, because this defect in gdb has been fixed.
>>
>> Brian
>
> Actually, is this really a fault in gdb? Cygwin is throwing a SIGSEGV
> signal, correct? GDB does what it's told, stops on SIGSEGV by default.
>
> -cl
But it doesn't interact properly with cygwin's exception handling -> signal
mechanism, and the task dies, when it should just run on.
Anyone who's doing any serious debugging on Cygwin very seriously wants to
build their own gdb and insight from current CVS. It's much improved of late.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
