This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: How does GDB informs remote stub about '^Cremote_interrupt called'
- From: Alexander Stante <mrpac at gmx dot de>
- To: Modi Banti <b dot modi at sssup dot it>
- Cc: gdb at sources dot redhat dot com
- Date: Sun, 11 Jul 2004 07:32:42 +0200
- Subject: Re: How does GDB informs remote stub about '^Cremote_interrupt called'
- References: <web-4863983@sssup.it>
Modi Banti wrote:
I am building a remote stub for an Arm simulator. I am using sockets to
communicate with GDB. when I want to break my program using through GDB(
C -c) I cann see the message ' ^Cremote_interrupt called' in GDB but I
dont get any packets in my reomte stub. I am not sure how GDB informs
the remote target to stop? does anybody have any idea about this?
I added a GdbStub for a game console emulator on which the actual code
for debugging is running on. But instead of sockets I used pipe to
communicate. In this case gdb just sends a ^C to the emulator which
leads to a SIGINT signal. I just had to wrote a SIGINT handler for the
emulator to get this working correctly. The handler just sets a Variable
to '1' and the Emulator checks at a certain point. If it is sets and
handels control over to the "main" function of the stub where all the
command processing is done. Not exactly the case you have but maybe that
helps.
Bye
Alex