Re: [MinGW-dvlpr] GDB 6.8

[Christopher F. <me...@cg...>]

On Mon, Apr 07, 2008 at 10:30:11AM -0700, Brandon Sneed wrote:
>On Apr 6, 2008, at 8:42 PM, Christopher Faylor wrote:
>>> I'll give your patch a try, though.  At least it's a start.
>>
>> I've applied the patch which Pedro Alves posted to the gdb mailing  
>> list
>> and that did not solve my I/O error problem.  I tracked the problem
>> down to a new requirement for setting a global "stop_soon =  
>> STOP_QUIETLY;"
>> in the win32-nat.c function "do_initial_win32_stuff".  That change  
>> is in
>> the recently-released cygwin gdb and I'll be checking it into the  
>> trunk
>> soon.
>>
>
>Thanks for looking into this Chris.  I found Pedro's patch, and it  
>appears to be much more thorough than mine.  Do you know what the  
>reasons are for Pedro's patch to not be included?

I don't really know but I assume that the second round of his patch is
just a round tuit problem, i.e., someone with global privileges has to
inspect it and pass judgement on it.

>I can't tell from the discussion there.  Or is it perhaps that your
>changes make the original patch non-applicable?

No, AFAICT, my changes are unrelated.  I had to make them because some
fairly major breakpoint-related changes were added to inflow.c in the
last few months and they (apparently) broke some assumptions that I was
making in win32-nat.c.  I think Pedro's changes are still required,
though.  For my particular workflow which consists of

    (gdb) dll cygwin1.dll
    (gdb) bp <somewhere in cygwin1.dll>
    (gdb) r
    *hit the breakpoint*

I only need my changes.  Setting a breakpoint where there aren't any
symbols loaded yet is a slightly different scenario.

cgf