From: "Decker, Paul" <Paul.Decker@analog.com>
To: <gdb@sources.redhat.com>
Subject: protocol question
Date: Tue, 22 Mar 2005 15:25:00 -0000 [thread overview]
Message-ID: <E21A9A52FF03B249B20F0DC563DEBB3117094DE7@nwd2exm3.ad.analog.com> (raw)
Hello everyone!
I apologize if this is the wrong news group for this question, if so;
just point me to the correct one.
I'm developing a target stub for a custom processor which will then be
able to connect with GDB. From what I understand, the stub can send
unsolicited messages to GDB, for example, if the stub encounters an
error of some sort, or wants to send other information to be displayed
in the GDB console. It seems this is done with the 'O' command being
sent by the stub, without the stub checking for an ack.
Is there anything in GDB that needs to be 'turned on' to enable this
functionality, or do I have a conceptual problem and this is not how it
is designed to work? I've tried to send a test command of:
// output of send text function
$O0a54686973206973206120746573740a#32
Just for testing, I'm doing this in the main processing loop
//process gdb proxy commands
while( pSocketObject->Getpkt(m_Threadbuff) > 0 )
{
nStatus = pSocketObject->ProcessCommand(m_Threadbuff);
if(nStatus > 0)
{
pSocketObject->Putpkt(m_Threadbuff);
}
pSocketObject->SendText("\nThis is a test\n");
//test for kill command
if(nStatus == -1)
{
break;
}
}
However, I don't get anything being printed in the gdb console. Any
ideas?
Thanks for any help!
Regards,
Paul.
next reply other threads:[~2005-03-22 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 15:25 Decker, Paul [this message]
2005-03-22 15:32 ` Daniel Jacobowitz
2005-03-22 15:45 Decker, Paul
2005-03-22 15:46 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E21A9A52FF03B249B20F0DC563DEBB3117094DE7@nwd2exm3.ad.analog.com \
--to=paul.decker@analog.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox