You need arm-linux-gnueabihf-gdb and it needs to be the same as your compiler 
version used to build your executable. 

Regards,
John




> On Aug 1, 2017, at 1:44 PM, [email protected] wrote:
> 
> William etal,
> Pointing to Molloy was a good hint. I watched him do it and around minute 31 
> he starts into remote debugging. He uses Eclipse and some cross tool chain, 
> but I didn't watch that. I am using the TI CCS v7.2 on Windows 7x64 which is 
> Eclipse based, but not cross compiling with their included tools.
> My configuration is somewhat different from Molloy's. He is cross compiling 
> so the sources AND the binary are present on the dev machine with Eclipse. I 
> have only the sources on my dev machine since I compile on the BBB.
> Issue 1. When creating a remote debug configuration in CCS/Eclipse the Main 
> tab field "C/C++ Application:" apparently wants the local binary on the dev 
> machine. It isn't happy without it and won't move forward at all. If I drag 
> the binary from the BBB back to the dev workspace and point at it, it will go 
> on.
> What is the correct way to configure this environment (source and dbg on Win 
> dev host; source, binaries and gdbserver on BBB)?
> Issue 2. So with a copy of the application binary on the dev host, launching 
> a remote debugging session leads to a gripe from the gdbserver about not 
> understanding the MI command list-features.  The console shows the connection 
> on the BBB target successfully launches gdbserver with the configured port, 
> the absolute path to the executable and the arguments. After the "listening 
> on port 2345" echo it terminates with the gripe about the MI command.
> Groping der google suggests this is often due to not having the correct 
> architecture gdb on the dev host selected. When installing CCSv7 I picked 
> only the arm tools for the AM33xx family processor. In the debug 
> configuration debugger tab main tab GDB debugger is the default setting 
> "gdb".  There is a Browse button to go looking through the installed 
> ti/ccsv7/tools/compiler, but the only gdb in the TI tools I can find is 
> C:\ti\ccsv7\tools\compiler\gcc-arm-none-eabi-6-2017-q1-update\bin\arm-none-eabi-gdb.exe.
>  that gdb echoes as it starts "This GDB was configured as 
> "--host=i686-w64-mingw32 --target=arm-none-eabi"." then warns "warning: A 
> handler for the OS ABI "GNU/Linux" is not built into this configuration of 
> GDB. Attempting to continue with the default arm settings." It then quits 
> with a complaint that no source was available.
> Maybe this is really a TI CCS specific setting. Earlier John pointed to CCS 
> so maybe he can provide some direction.
> Thanks,
> Hugh
> 
> On Thursday, July 27, 2017 at 4:14:58 PM UTC-7, William Hermans wrote:
> 
> 
> On Thu, Jul 27, 2017 at 4:13 PM, William Hermans <[email protected] 
> <javascript:>> wrote:
> This is probably the best guide you're going to find on the subject.
> 
> https://www.youtube.com/watch?v=T9yFyWsyyGk 
> <https://www.youtube.com/watch?v=T9yFyWsyyGk>
> 
> Never used it myself( I do not cross compile ), but I'm confident DR Molly's 
> instructions work.
> 
> Just in case it's not clear, R Molly shows how to setup remote debugging 
> towards the end I think. Been a while since I've watched this. 
> 
> 
> -- 
> For more options, visit http://beagleboard.org/discuss 
> <http://beagleboard.org/discuss>
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/fa591c36-14bb-4237-8286-0076e36c4407%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/beagleboard/fa591c36-14bb-4237-8286-0076e36c4407%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/587433A3-9E03-428E-A642-A003BB9EF79D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to