RE: Rygel-0.32.1 will not stream outside the gnome evironment



Apparently the discovery process gets stuck then. Can you run it 
inside gdb and get a "thread apply all bt" output? Thanks.

Maybe I'm being dense, but if rygel does not crash, how can I get a 
"thread apply all bt" output?

Just CTRL-C (aka send SIGINT) it.

Also just do gdb on mx-extract, so:

gdb --args /usr/local/libexec/mx-extract --extract-metadata EXTRACT file:///....

then CTRL-C
and t a a bt

I don't really get anything useful from this - perhaps because the c libs are stripped, but:

(gdb) run rygel
Starting program: /usr/local/bin/rygel rygel
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be 
available.
[New LWP 15112]
[New LWP 15114]
Rygel-Message: rygel-acl.vala:143: No ACL fallback policy found. Using "allow"
[New LWP 15115]
Rygel-Message: Rygel v0.32.1 starting?
[New LWP 15116]
RygelCore-Message: New plugin 'MediaExport' available
MediaExport-Message: rygel-media-export-extract.vala:163: Started with descriptors 3 (in) 4 (out)
MediaExport-Message: rygel-media-export-extract.vala:163: Started with descriptors 3 (in) 4 (out)
MediaExport-Message: rygel-media-export-extract.vala:163: Started with descriptors 3 (in) 4 (out)
[New LWP 15123]
[New LWP 15125]
MediaExport-Message: 'file:///home/tc/Pictures' harvested
MediaExport-Message: rygel-media-export-harvesting-task.vala:300: Harvesting of file:///home/tc/Pictures done 
in 0.107498
MediaExport-Message: rygel-media-export-extract.vala:163: Started with descriptors 3 (in) 4 (out)
[LWP 15114 exited]
[LWP 15125 exited]
[LWP 15123 exited]
[LWP 15115 exited]
^C
Thread 1 "rygel" received signal SIGINT, Interrupt.
0x76a8bf40 in poll () from /lib/libc.so.6
(gdb) t a a bt

Thread 5 (LWP 15116):
#0  0x76a8bf40 in poll () from /lib/libc.so.6
#1  0x00000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (LWP 15112):
#0  0x76a8bf40 in poll () from /lib/libc.so.6
#1  0x00000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (LWP 15108):
#0  0x76a8bf40 in poll () from /lib/libc.so.6
#1  0x00000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]