[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-debug-dev] Gdbserver connection problem -- Reply contains invalid hex digit 59
|
CDT 'launches' the debugger named in the Main tab of the launch configuration
dialog. By default, it is "gdb", but you can change it to anything you like.
(BTW: if you use the 'Zylin' plugin, the name of the debugger can be specified
via a preference. See http://www.zylin.com/embeddedcdt.html).
To 'launch' an application, it (eventually) uses exec(), so the debugger should
be present on your systems' path. Alternatively, you specify the fully qualified
pathname.
--
Derek
Bulent Egrilmez wrote:
Thanks for the answers though it was not relevant to CDT
But I guess this one might be relevant , what is the easiest way of
changing the GDB used by CDT to another custom gdb?
Does CDT use the global path'd cygwin gdb?
Regards,
Bulent
-----Original Message-----
From: cdt-debug-dev-bounces@xxxxxxxxxxx
[mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Derek Morris
Sent: 07 February 2007 19:05
To: CDT Debug developers list
Subject: Re: [cdt-debug-dev] Gdbserver connection problem -- Reply
contains invalid hex digit 59
What happens when you run the same commands from the command line? If
you get the same (or similar) behavior, it is definitely outside of the
scope of CDT.
If you get different behavior, I suggest you turn on Verbose console
mode in your launch configuration and trace through the MI
command/response to help trace it through.
HTH
--
Derek
Bulent Egrilmez wrote:
Hi ,
I am having problem to use CDS over a STB target which has a MIPS32
core
I receive this message
Couldn't establish connection to remote target
Reply contains invalid hex digit 59
whilst I receive the following message on the target
# gdbserver host:6789 --attach 51
Attached; pid = 51
Listening on port 6789
Remote debugging from host 10.178.6.253
readchar: Got EOF
Remote side has terminated connection. GDBserver will reopen the
connection.
Listening on port 6789
any ideas what is going wrong?
Thanks in advance
Regards,
//
//
/*Bulent Egrilmez*/
------------------------------------------------------------------------
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev