[maemo-developers] Debugging the browser

[From: Eero Tamminen]

Hi,

ext Akos Putz wrote:
> I'm currently experimenting with npapi-compatible browser plugin
> programming on the N800. My problem is, that debugging the browser
> triggers some interesting gdb error message, see below:
> 
> ~ $ gdb maemo-summoner
> GNU gdb 6.4
> Copyright 2005 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "arm-linux-gnueabi"...(no debugging symbols found)
> Using host libthread_db library "/lib/libthread_db.so.1".
> 
> (gdb) r /usr/bin/browser.launch
> Starting program: /usr/bin/maemo-summoner /usr/bin/browser.launch
> (no debugging symbols found)
> (no debugging symbols found)
> BFD: /usr/lib/debug/lib/libc-2.3.6.so: warning: sh_link not set for
> section `.ARM.exidx'

These should be harmless.


> (no debugging symbols found)

You need debug symbols for everything, otherwise Gdb shows wrong
function names (without information about static functions, it shows
name of the "nearest" exported function) and cannot backtrace
stacktraces.


> WARNING: osso_application_set_exit_cb() is obsolete and a no-op.
> [New Thread 32769 (LWP 2621)]
> [New Thread 16386 (LWP 2622)]
> [Thread 16386 (LWP 2622) exited]
> Cannot find thread 16386: invalid thread handle

Especially C/thread library debug symbols...


> (gdb) q
> The program is running.  Exit anyway? (y or n) y
> 
> ...and at this point, gdb freezes.

If you try to strace the frozen Gdb process, what that reports?


> Note: using the opera8 backend (the microB seems to work almost fine,
> btw), and my plugin is not yet installed, so it cannot be the cause.
> 
> Any thoughts?


	- Eero