Figure out what parts of the program are suspect and instrument it with debug output.
Lots of real work has been done on systems that don't have debuggers available, simply by analytic thinking and adding instrumentation on the things that can go wrong. On Oct 19, 7:20 am, Junaid Rana <mrjai...@gmail.com> wrote: > Hello > > I have synchronized repo and have made the source successfully. Now i > am trying to debug rild.c and reference-ril.c but i am unable to do > so. > > I tried each of the following to debug these > 1- C/C++ Eclipse IDE > 2- gdb > 3- A method given in the following > linkhttp://source.android.com/porting/debugging_gdb.html > > But none of the above really worked. > The most close thing was the method given in this link but when i > write > gdbserver :5039 /system/bin/rild > > i get an error that access to this service (rild) is not permitted. > > Can anyone help me through this issue. > Thanking in advance > > Regards > Junaid Rehmat. -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
