Hi again, sometimes one can`t see the obvious, but thanks for help. I connected gdb remote. But I got following message:
warning: The current binary is a PIE (Position Independent Executable), which GDB does NOT currently support. Most debugger features will fail if used in this session. Reading symbols from /home/joerg/prj/OpenMoko/shr/shr-build/shr-unstable/tmp/work/armv4t-oe-linux-gnueabi/bluez4-4.59-r5.0/bluez-4.59/src/.libs/bluetoothd...done. (gdb) target remote 192.168.0.202:3333 Remote debugging using 192.168.0.202:3333 warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. and I cannot set breakpoints or whatever. I thought, gdb 7.0 is supporting PIE. Is there any possibility to compile bluez4 not as PIE, would it work? While googeling, I found some patches for gdb, which may help. Any ideas? (by the way, is there a usable graphical frontend for gdb for this case: remote-debugging wit cross gdb)? I only managed to get it running (until the message) textbased. Thank you for supporting me, best regards, Joerg On Fri, 2010-01-08 at 14:39 -0800, Khem Raj wrote: > On (08/01/10 22:37), Joerg Eesmann wrote: > > Hi there, > > I am trying to remote debug my Openmoko freerunner. > > I already installed succesfully gdbserver, and can attach it to the > > progem I am going to debug. > > The question is, what to do on host side? > > I bitbaked gdb-cross-sdk, I bitbaked my changed package (bluez4) > > So I will install a debug version of the package, and attach to the > > bluetoothd-demon. > > On host side, I guessed I needed a gdb, that can handle ARM-processor, > > therefore gdb-cross-sdk. > > Now I should have everything... but a few questions left. > > GDB ist only ipk-package, what to do with this? > > you need gdb-cross once you build that you should be able to use it > from same place as cross gcc. > > > Where do I find the arm-compiler bluetoothd on my host (I guess in work, > > but will this be the strippded version or not, because also stripped > > package has been made). > > Am I on the right way? Is there any howto or something like that > > availlable, where you could point me? > > > > if you build it then the non stripped version should be there in > your workdir (where the package was built) > > -Khem > > thank you for your help in advance, > > best regards, > > Joerg > > > > > > > > _______________________________________________ > > Openembedded-devel mailing list > > [email protected] > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
