Quoting Thomas Erdmann <[EMAIL PROTECTED]>: > > Thats strange. > > To locate the source of the crash, you should run vdr from gdb. For example > > # gdb ./ vdr > > > > This is the output of trying to do full screen with the "f" key, > vdr started under control of gdb 'vdr -Psoftdevice .....`:
But that's not the sequence I intendet to asked for. Command I wrote is buggy. From vdr's directrory I do: jarada vdr-1.4.0.jarada # gdb ./vdr 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 "i686-pc-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) set args -P "softdevice -vo xv:" -E /net_data/vdr137-dvb-t-jarada/epg.data -c /net_data/vdr137-dvb-t-jarada -v /net_data/video/ -p 2010 (gdb) run Starting program: /home/nfs/extra/src/video/DVB/vdr-1.4.0.jarada/vdr -P "softdevice -vo xv:" -E /net_data/vdr137-dvb-t-jarada/epg.data -c /net_data/vdr137-dvb-t-jarada -v /net_data/video/ -p 2010 [Thread debugging using libthread_db enabled] > VDR terminates when pressing f and gdb shows "No stack". > Any hints ? Which messages were written to syslog (/var/log/messages or /var/log/syslog, depending on your distribution). Stefan Lucke _______________________________________________ Softdevice-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/softdevice-devel
