Re: [N900] Yes, another hildon-home bug thread...
 

Another person who faced the problem that peterleinchen described:
-Hildon-home popup that it is not responding
-Hildon-home in a freeze state, you can scroll but the widgets are "frozen", you cannot click them (includes shortcuts)

My installed and active widgets:
- Default Calendar widget
- 3x ConnectNow widget with 3 wifi APs
- Desktop Clock Widget
- Default mediaplayer widget
- Sticky Notes widget
- Few qbw: Here I explained which ones: http://talk.maemo.org/showthread.php?p=1255342
That's generally my whole desktop setup

All QBW only update click with exception of(updated on desktop):
Max - CPU-Freq
IP
uptime
battery percentage

I suspect one of these to let H-h freeze

Re: [N900] Yes, another hildon-home bug thread...
 

Well, install gdb and debug symbols and next time h-h is frozen just attach gdb and check where it iterates. Post the backtrace here and we all will be happy :)

Re: [N900] Yes, another hildon-home bug thread...
 

@mr_pingu
You do not have DCEW installed, it seems? But QBW.
And we are using about the same commands (IP, uptime, ...).
What we have in common is only mediaplayer and cal-home-widget.

I suspected DCEW to be the bad guy, but it seems it is just bad h-h implementation!?

Do you remember which desktop was shown, when this happened?
I cannot, but guess it was my first with cal-home-widget and a bunch of DCEW commands (IP, uptime, batt, ...).

Re: [N900] Yes, another hildon-home bug thread...
 

Hey freeman,
did not see your post in between.

Many thanks in advance for your efforts.

I do have gdb installed and just did so with h-h-dbg.
But the last time I used gdb was 15 years ago and even then I did not understand it very well ;)

So i fetched process id of h-h with
~ $ ps |grep home
1515 user 3932 T /usr/bin/hildon-home
1519 user 120m S /usr/bin/hildon-home
1998 user 29300 S /usr/bin/osso-abook-home-applet
23706 user 2844 S grep home

But both process IDs show that I attach with gdb to /usr/bin/maemo-invoker, not h-h.

So can you give us a short guide how to get the info you need, like
ps | grep home
fetch ID
gdb
attach ID
backtrace
and then post output...
Or?

--edit
with id 1519 I did not see any info
(gdb) attach 1519
Attaching to program: /usr/bin/maemo-invoker, process 1519
(no debugging symbols found)
(no debugging symbols found)
0x4018d798 in ?? ()
0x4018d798: cmn r0, #4096 ; 0x1000
(gdb)

with 1515 I saw a lot of libs loaded (all without dbg syms), but none essential
(gdb) detach
Detaching from program: /usr/bin/maemo-invoker, process 1515
(gdb) attach 1519
Attaching to program: /usr/bin/maemo-invoker, process 1519
(no debugging symbols found)
(no debugging symbols found)
0x4018d798 in ?? ()
0x4018d798: cmn r0, #4096 ; 0x1000
(gdb) detach
Detaching from program: /usr/bin/maemo-invoker, process 1519
(gdb) attach 1515
Attaching to program: /usr/bin/maemo-invoker, process 1515
Reading symbols from /usr/lib/libjpeg.so.62...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libjpeg.so.62
Reading symbols from /usr/lib/libgvfscommon.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgvfscommon.so.0
Reading symbols from /lib/libc.so.6...Reading symbols from /usr/lib/debug/lib/libc-2.5.so...(no debugging symbols found)...done.
(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /usr/lib/libdbus-1.so.3...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libdbus-1.so.3
Reading symbols from /lib/libpthread.so.0...Reading symbols from /usr/lib/debug/lib/libpthread-2.5.so...(no debugging symbols found)...done.
[Thread debugging using libthread_db enabled]
(no debugging symbols found)...done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /usr/lib/libgio-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgio-2.0.so.0
Reading symbols from /usr/lib/libgobject-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgobject-2.0.so.0
Reading symbols from /usr/lib/libglib-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libglib-2.0.so.0
Reading symbols from /lib/ld-linux.so.3...Reading symbols from /usr/lib/debug/lib/ld-2.5.so...(no debugging symbols found)...done.
(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.3
Reading symbols from /lib/librt.so.1...Reading symbols from /usr/lib/debug/lib/librt-2.5.so...(no debugging symbols found)...done.
(no debugging symbols found)...done.
Loaded symbols for /lib/librt.so.1
Reading symbols from /usr/lib/libgmodule-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgmodule-2.0.so.0
Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/libdl.so.2...Reading symbols from /usr/lib/debug/lib/libdl-2.5.so...(no debugging symbols found)...done.
(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
0x401206cc in read () from /lib/libc.so.6
0x401206cc <read+28>: mov r7, r12
(gdb) backtrace
#0 0x401206cc in read () from /lib/libc.so.6
#1 0x000099dc in ?? ()
#2 0x000099dc in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Re: [N900] Yes, another hildon-home bug thread...
 

@peterleinchen - for start install libc6 debug symbols, then continue to attach/detach/install debug symbols for every library in the backtrace which is missing them.

Have in mind that libc6 debug symbols are in SDK repo, you'll need to enable it.

The correct process ID is always the bigger one, 1519 in the case above

BTW I am on #maemo, join if you wish for some "online support" :)

EDIT:

And you definitely want to install hildon-home-dbg package ;)

EDIT2: sorry, had missed the "h-h-dbg" part in your post

Re: [N900] Yes, another hildon-home bug thread...
 

Somehow I already had libc6-dbg installed :confused: (maybe crash-reporter?).
Do I really need to load all symbol libs? OK, if it occurs in one of those libs, then of course (and I will continue to fetch missing symbols).


Assumed so, but now I know.

Thanks for the offer. But until now it is just setup. Maybe will come back to your offer later, when I could reproduce and fetch more info.
But I have no idea why and when this happens. So it may take weeks to run again into it (and hopefully I can remember then (quite older now ;)) and I do have the time/opportunity to check out.
Hopefully mr_pingu (or others) may also help out ...

Sure thing, no prob :)


--edit
BTW now I get dozens of symbols loaded, but at the beginning the output looks like there are still missing a few. Need to fetch full output of gdb anyway ...

Re: [N900] Yes, another hildon-home bug thread...
 

gdb will load them for you, you don't have to load them by hand, but you have to have them installed.

Well, having to wait for a week or two is nothing compared to the date of the first post in this very thread :)

Re: [N900] Yes, another hildon-home bug thread...
 

I don't mind some testing but I still have only one device so I would like to know the impact of gdb and the debug-symbols for a day to day use phone ;)

If the impact is not that big, I will bother you, freemangordon, on IRC to get this thing up. I never used gdb before...

Re: [N900] Yes, another hildon-home bug thread...
 

The only possible impact is rootfs space usage. Though you can move debug symbols to /opt and symlink

Re: [N900] Yes, another hildon-home bug thread...
 

That's no problem then, right now I have 78MB free. Also, after we got the logs we want we can remove the -dev, right? :)

Do you have time to help me, right now?