[maemo-developers] maemo - zoom2 - worldclock

[From: john.beattie at accenture.com]

OK, I've just checked that:

OMAPZOOM2:~# dpkg -l | grep clock
ii  clock-ui                                            0.5.32-1+0m5                    UI part of the clock
ii  clockd                                              0.0.36+0m5                      Clock daemon
ii  libclockcore0-0                                     0.5.15-1+0m5                    Back-end library for Clock Application
ii  libtime-dev                                         0.0.36+0m5                      Development files for clockd services
ii  libtime0                                            0.0.36+0m5                      API for clockd service

[plus lots of language packages for the clock]

OMAPZOOM2:~# ps | grep clockd
 1143 root      3336 S    /usr/bin/clockd
 3257 root      2092 S    grep clockd
OMAPZOOM2:~#

The following is way more information than you asked for :-)

For completeness, the hang is obtained by selecting the clock, then the dropdown menu, then the alarm settings, then alarm tine, then select one of the clock alarm buttons. 

If gdb is attached to the app first, then at the time that the final select is done, there is a message that a new LWP has been started and immediately that it quits.

The hang is fixed in the end by a monitor whch observes that the task is not responding and asks of you want to quit.

And this is some of the trace from gdb: (note that there may be spurious linefeeds in this)

gdb) bt
#0  0x401896ec in poll () from /lib/libc.so.6
#1  0x402f80a0 in g_poll () from /usr/lib/libglib-2.0.so.0
#2  0x402ead74 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x402ead74 in ?? () from /usr/lib/libglib-2.0.so.0
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) c
Continuing.
[New LWP 1990]
[LWP 1990 exited]

Program received signal SIGINT, Interrupt.
0x401852f8 in chown () from /lib/libc.so.6
0x401852f8 <chown+16>:  cmn     r0, #4096       ; 0x1000
(gdb) bt
#0  0x401852f8 in chown () from /lib/libc.so.6
#1  0x41142a70 in pa_make_secure_dir () from /usr/lib/libpulsecommon-0.9.15.so
#2  0x41142bcc in pa_get_runtime_dir () from /usr/lib/libpulsecommon-0.9.15.so
#3  0x4114313c in ?? () from /usr/lib/libpulsecommon-0.9.15.so
#4  0x4114313c in ?? () from /usr/lib/libpulsecommon-0.9.15.so
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) c
Continuing.

Program received signal SIGINT, Interrupt.
0x40081da4 in pthread_cond_timedwait () from /lib/libpthread.so.0
0x40081da4 <pthread_cond_timedwait+452>:        mov     r8, r0
(gdb)  bt
#0  0x40081da4 in pthread_cond_timedwait () from /lib/libpthread.so.0
#1  0x429e60dc in gstreamer_driver_play ()
   from /usr/lib/libcanberra-0.14/libcanberra-gstreamer.so
#2  0x411d7438 in ?? () from /usr/lib/libcanberra.so.0
#3  0x411d7438 in ?? () from /usr/lib/libcanberra.so.0
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) c
Continuing.

Program received signal SIGINT, Interrupt.
0x40081da4 in pthread_cond_timedwait () from /lib/libpthread.so.0
0x40081da4 <pthread_cond_timedwait+452>:        mov     r8, r0
(gdb) bt
#0  0x40081da4 in pthread_cond_timedwait () from /lib/libpthread.so.0
#1  0x429e60dc in gstreamer_driver_play ()
   from /usr/lib/libcanberra-0.14/libcanberra-gstreamer.so
#2  0x411d7438 in ?? () from /usr/lib/libcanberra.so.0
#3  0x411d7438 in ?? () from /usr/lib/libcanberra.so.0
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) c
Continuing.

Program received signal SIGABRT, Aborted.
0x400fb4b8 in raise () from /lib/libc.so.6
0x400fb4b8 <raise+68>:  cmn     r0, #4096       ; 0x1000
(gdb)






-----Original Message-----
From: Carsten Munk [mailto:carsten.munk at gmail.com] 
Sent: 24 February 2010 13:56
To: Beattie, John
Cc: maemo-developers at maemo.org
Subject: Re: maemo - zoom2 - worldclock

I'm going to make an educated guess that it is due to the lack of
clockd on Zoom2 (check with dpkg -l)

/Carsten
maemo.org distmaster

2010/2/24 John Beattie <john.beattie at accenture.com>:
>
> I'm learning about maemo using zoom2 hardware.  I have a bug where worldclock
> hangs when I make a certain sequence of user-input. I have used gdb to see
> what is going on, but without source, since this is a closed package, the
> clock-ui package.  It looks as if the app spawns a thread to do something
> and then starts pthread_cond_timedwait. And then the thread quits very
> quickly and the originating thread never progresses.
>
> My question is whether it is worth raising this as an issue, since the zoom2
> is only for development hacking and, further, my build is not anything like
> an official maemo release?
> --
> View this message in context: http://n2.nabble.com/maemo-zoom2-worldclock-tp4625849p4625849.html
> Sent from the maemo-developers mailing list archive at Nabble.com.
> _______________________________________________
> maemo-developers mailing list
> maemo-developers at maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>



This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information.  If you have received it in error, please notify the sender immediately and delete the original.  Any other use of the email by you is prohibited.