* what is the mean of remote protocol "S 00"?
@ 2013-01-31 8:03 horseriver
2013-02-01 20:39 ` Pedro Alves
0 siblings, 1 reply; 4+ messages in thread
From: horseriver @ 2013-01-31 8:03 UTC (permalink / raw)
To: gdb
hi:)
When using remote debug, target reply a "S 00" packet to gdb side,
I know this is a signal notify.
what will gdb do for signal 0?
thanks!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: what is the mean of remote protocol "S 00"?
2013-01-31 8:03 what is the mean of remote protocol "S 00"? horseriver
@ 2013-02-01 20:39 ` Pedro Alves
2013-02-02 4:43 ` John Smith
0 siblings, 1 reply; 4+ messages in thread
From: Pedro Alves @ 2013-02-01 20:39 UTC (permalink / raw)
To: horseriver; +Cc: gdb
On 01/30/2013 10:20 PM, horseriver wrote:
> hi:)
>
> When using remote debug, target reply a "S 00" packet to gdb side,
>
> I know this is a signal notify.
>
> what will gdb do for signal 0?
signal 0 means the target stopped with no signal at all.
It just stopped. GDB will just say the target stopped.
--
Pedro Alves
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: what is the mean of remote protocol "S 00"?
2013-02-01 20:39 ` Pedro Alves
@ 2013-02-02 4:43 ` John Smith
2013-02-04 10:38 ` David Paterson
0 siblings, 1 reply; 4+ messages in thread
From: John Smith @ 2013-02-02 4:43 UTC (permalink / raw)
To: Pedro Alves, gdb
That is saying I can not know the stop reason ?
In this case , gdb will stop at the $eip in "g" packet， which is sent
from the target side ?
Is there method to know why the target stoped?
Thanks！
2013/2/2 Pedro Alves <palves@redhat.com>:
> On 01/30/2013 10:20 PM, horseriver wrote:
>> hi:)
>>
>> When using remote debug, target reply a "S 00" packet to gdb side,
>>
>> I know this is a signal notify.
>>
>> what will gdb do for signal 0?
>
> signal 0 means the target stopped with no signal at all.
> It just stopped. GDB will just say the target stopped.
>
> --
> Pedro Alves
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: what is the mean of remote protocol "S 00"?
2013-02-02 4:43 ` John Smith
@ 2013-02-04 10:38 ` David Paterson
0 siblings, 0 replies; 4+ messages in thread
From: David Paterson @ 2013-02-04 10:38 UTC (permalink / raw)
To: John Smith; +Cc: Pedro Alves, gdb
On 2 February 2013 04:43, John Smith <horserivers@gmail.com> wrote:
> That is saying I can not know the stop reason ?
> In this case , gdb will stop at the $eip in "g" packet， which is sent
> from the target side ?
> Is there method to know why the target stoped?
That really depends on your target and remote server.
You might be able to work out the reason by examining the call stack, or
looking at status or trap registers if your hardware has such things.
If the remote server can't give you a better indication of the stop reason, then
perhaps it's not possible to work it out, and it defaults to "00".
Regards,
David P.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-02-04 10:38 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-01-31 8:03 what is the mean of remote protocol "S 00"? horseriver
2013-02-01 20:39 ` Pedro Alves
2013-02-02 4:43 ` John Smith
2013-02-04 10:38 ` David Paterson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox