View Single Post
Old 01-27-2015, 05:25 AM   #61
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,982
Karma: 18343081
Join Date: Oct 2010
Location: Sudbury, ON, Canada
Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840, PB 633
Quote:
Originally Posted by mikmak View Post
Hm, ok. Is there any way I can further debug this on the PB 630? In the crash log only "segmentation fault" is reported, so not really helpful.
Not easily. There's a thread in the development forum where I gave some tips on running gdb on the devices. Running gdb remotely is a pain, though. And running it locally doesn't seem possible since none of the terminals seem to be able to support it. However, I've found that you can set up a file of input commands to gdb to run the program and then print out the stack frame where the crash took place, and redirect standard input for gdb to that file. In this case, though, I'm not sure which process you should run the debugger on. The event forwarder? Some lua interpreter? Who knows.
rkomar is offline   Reply With Quote