View Single Post
Old 04-08-2014, 01:30 PM   #2
rkomar
Wizard
rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.
 
Posts: 2,574
Karma: 9120778
Join Date: Oct 2010
Location: Sudbury, ON, Canada
Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840
I just discovered today that gdb runs fine within the pbterm application. So, if you can use pbterm as your commandline interface, then you don't need to do remote debugging via gdb.

You need to install gdb, libncurses.so.5 and libreadline.so.5 from the debian lenny armel distribution. Install gdb to /mnt/ext1/system/bin. Install the two libraries to /mnt/ext1/system/lib. Then within pbterm on the device:

export LD_LIBRARY_PATH=/mnt/ext1/system/lib
export PATH=/mnt/ext1/system/bin:$PATH
gdb <program-path>

You can use the multi-task menu on the device to switch between pbterm and the application if necessary.

I've provided the gdb binary and the two libraries that I copied from the debian lenny armel distribution as an attachment. Sources for those are available in the debian archives.
Attached Files
File Type: zip gdb.zip (1.30 MB, 260 views)
rkomar is offline   Reply With Quote