Re: gdb on arm-wince-pe

[Pedro Alves <pedro_alves@portugalmail.pt>]

Christopher Faylor wrote:

>On Tue, Feb 21, 2006 at 11:40:09PM -0500, Daniel Jacobowitz wrote:
>  
>
>>On Tue, Feb 21, 2006 at 08:41:48PM +0000, Pedro Alves wrote:
>>    
>>
>>>Where should I start looking for/what is needed to implement it (ctrl_c 
>>>breaking)?
>>>I tried debugging arm-wince-pe-gdb on gdb itself, putting some 
>>>breakpoints in the signal handling,
>>>and issuing kill -INT signals to see what happens there, and I see that 
>>>ultimatly, quit (void) is called.
>>>Is there some target_op that I should implement, or should I provide my 
>>>own signal handling?
>>>      
>>>
>>Take a look at remote.c, which installs its own signal handler.  You'll
>>want to do something similar.
>>
>>Really, if possible, I would recommend using remote.c to talk to your
>>target over the standard GDB remote protocol instead of the
>>WinCE-specific protocol that wince-stub.c implements.  That's much
>>better supported.
>>    
>>
>
>As the author of the WinCE-specific protocol, I agree 100%.  Really, I
>think that the WinCE targets should be deprecated since they no longer
>have a maintainer.
>
>cgf
>
>  
>
Ok, thanks for the quick replies. I'll see what I can do.

Cheers,
Pedro Alves