I remember someone saying that GDB for the BBB ( perhaps the whole ARCH ) Does not work properly. This was last year though.
Which port are you using for the C GDBServer ? From what little you describe it almost sounds like a connection issue, because of too low a port, and a possible myriad of other things. Giving us the EXACT error message as given to you on the command line would certainly help *some* But as John said, you may want to consider moving to Debian just because most people are using it now, or will be. On Wed, May 28, 2014 at 12:44 PM, John Syn <[email protected]> wrote: > > From: Simon Platten <[email protected]> > Reply-To: <[email protected]> > Date: Wednesday, May 28, 2014 at 12:09 PM > To: <[email protected]> > Subject: Re: [beagleboard] Eclipse C and Remote Debugging > > I'm still looking for a solution and getting more and more frustrated by > what seems to be a very steep up hill battle. > > There are quite a few sites linking to > http://www.angstrom-distribution.org/toolchains/ > > I think you are going to find it harder and harder to get support for > Angstrom. It has been over a year since I’ve used Angstrom so I don’t every > remember how to get some things working. I would recommend that you make > the move to Debian as we are much more able to help with the OS we > currently use. > > Regards, > John > > > This link is invalid and results in a 404. The toolchains that I did > manage to track down are not all complete, some have a gdb in the archive, > others don't. > > Can someone point me in the direction of a complete toolchain with > instructions on how to install it correctly? > > Thank you, > Simon > > On Wednesday, 28 May 2014 08:52:36 UTC+1, Simon Platten wrote: >> >> Hi John, Thank you for the reply, perhaps I wasn't very clear. GDB >> Server is installed on the Beaglebone Black and I see the process running, >> it just fails to connect. >> >> I will post more detail when I get home tonight. I've tried using the >> default port 2345 and also found a post suggesting 3333, neither worked. >> >> >> >> On Wednesday, 28 May 2014 08:45:53 UTC+1, john3909 wrote: >>> >>> >>> From: Simon Platten <[email protected]> >>> Reply-To: <[email protected]> >>> Date: Tuesday, May 27, 2014 at 11:53 PM >>> To: <[email protected]> >>> Subject: [beagleboard] Eclipse C and Remote Debugging >>> >>> I have Eclipse Kepler running on Ubuntu 14.04 x64, I can build and >>> remote debug Java applications on the Beaglebone Black, but for some reason >>> I cannot remote debug C applications. >>> >>> I can compile a C application and I can see that it is transferred to >>> the Beaglebone Black, I can even run it from an SSH terminal on the >>> Beaglebone Black. But trying to remote debug always fails with a GDB error. >>> >>> The console reports that GDB will reconnect, however it never does. >>> >>> I've tried following numerous videos on YouTube, however none of them >>> have resolved this issue. >>> >>> In the end I decided to build and compile on the Beaglebone Black >>> directly, however now I get an error saying GLIBC_2.17 libc.so.6 not >>> found...sorry if my post isn't very detailed, I'm at work now without >>> access to all the information. >>> >>> Can anyone point me in the right location to resolve either the remote >>> debugging or the GLIBC_2.17 error? I have already spent a very long time >>> trying to find answers myself. >>> >>> You need GDBServer installed on your BBB. You launch GDBServer on your >>> BBB with IP of host and specify the port number for the host to connect to. >>> In Eclipse, I don’t recall the exact command, but it is something like gdb >>> remote <BBB ipaddr> <BBB port>. There are plenty of example on Google. >>> >>> https://www.google.com/search?q=eclipse+gdbserver+remote+ >>> debug&oq=eclipse+gdbserver&aqs=chrome.1.69i57j0l5. >>> 16411j0j7&sourceid=chrome&es_sm=119&ie=UTF-8 >>> >>> Regards >>> John >>> >>> >>> >>> Thank you, >>> >>> Kind Regards, >>> Simon >>> >>> -- >>> 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]. >>> For more options, visit 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]. > For more options, visit 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]. > For more options, visit 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]. For more options, visit https://groups.google.com/d/optout.
