Re: [ATrpms-users] mythfilldatabase segfaulting
On Thursday 02 August 2007, Axel Thimm wrote: On Thu, Aug 02, 2007 at 09:21:19AM +0200, wouter lists wrote: Perhaps a stupid question: mythfilldatabase is a commandline tool to enter the data of a xml file into a database. Why does it need QT, which is a graphical library? QT has more than graphical entities in the lib. Not sure if I'm having the same issue, but I just found out mythfilldatabase also segfaults here and my guide is empty. Solved this. The tv_grab_nl script was wrong. I am using a different one than supplied, the one supplied segfaults. Unfortunately I have a very strange issue now. Although my system time is 2nd of august, mythtv runs one day ahead. I can't find out what's wrong. The TV guide is fine but just the date in mythtv is one day ahead of schedule. regards, Marcel ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
Re: [ATrpms-users] mythfilldatabase segfaulting
On Thursday 02 August 2007, Marcel Janssen wrote: Unfortunately I have a very strange issue now. Although my system time is 2nd of august, mythtv runs one day ahead. I can't find out what's wrong. The TV guide is fine but just the date in mythtv is one day ahead of schedule. output from mythfilldatabase : 2007-08-03 23:58:45.217 mythfilldatabase run complete. Segmentation fault- so still segfaulting but it seems to fill the database now. [EMAIL PROTECTED] marcel]$ date Thu Aug 2 23:59:19 CEST 2007 - this is correct. Obviously mythfilldatabase or xmltv is wrong. My guess is xmltv is wrong here. regards, Marcel ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
Re: [ATrpms-users] mythfilldatabase segfaulting
ok, second try 2007-07-30 14:12:15.370 Connecting to backend server: 127.0.0.1:6543 (try 1 of 5) 2007-07-30 14:12:15.370 Using protocol version 31 [New Thread 1084229968 (LWP 23674)] 2007-07-30 14:12:15.396 mythfilldatabase run complete. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 46912496270416 (LWP 23671)] 0x2e9031c0 in ?? () Thread 2 (Thread 1084229968 (LWP 23674)): #0 0x00328a6ca462 in select () from /lib64/libc.so.6 No symbol table info available. #1 0x003417e2a707 in MythSocket::readyReadThread () from /usr/lib64/libmyth-0.20.1.so.0 No symbol table info available. #2 0x00328b2062f7 in start_thread () from /lib64/libpthread.so.0 No symbol table info available. #3 0x00328a6d0fbd in clone () from /lib64/libc.so.6 No symbol table info available. Thread 1 (Thread 46912496270416 (LWP 23671)): #0 0x2e9031c0 in ?? () No symbol table info available. #1 0x003294d05473 in QApplication::~QApplication () from /usr/lib64/qt-3.3/lib/libqt-mt.so.3 No symbol table info available. #2 0x00431869 in QGList::~QGList$delete () No symbol table info available. #3 0x00328a61dab4 in __libc_start_main () from /lib64/libc.so.6 No symbol table info available. #4 0x00407309 in QGList::~QGList$delete () No symbol table info available. #5 0x7fffec8f7298 in ?? () No symbol table info available. #6 0x in ?? () No symbol table info available. Wouter ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
Re: [ATrpms-users] mythfilldatabase segfaulting
Hi Wouter, The mythtv people appreciate it if we provide a gdb backtrace. You can do that as follows: su - mythtv cat .gdbcmds EOF handle SIGPIPE nostop noprint handle SIG33 nostop noprint set logging on set pagination off set args -l myth.log -v record,channel,siparser --update --file 1 -1 run thread apply all bt full set logging off EOF gdb -x .gdbcmds /usr/bin/mythfilldatabase Good luck, Kim wouter lists wrote: Hi Axel, I just ran a complete update and I still have the problem. 2007-07-28 23:56:02.483 Connecting to backend server: 127.0.0.1:6543 (try 1 of 5) 2007-07-28 23:56:02.484 Using protocol version 31 2007-07-28 23:56:02.498 mythfilldatabase run complete. ./get_epg_1d.sh: line 12: 3170 Segmentation fault /usr/bin/mythfilldatabase --update --file 1 -1 /home/mythtv/jxmltv/xmltv.xml 2 /dev/null extract from dmesg: [drm] Loading R300 Microcode [drm] writeback test succeeded in 1 usecs mythfilldatabas[3169] trap invalid opcode rip:9f0381 rsp:409ff6a8 error:0 mythfilldatabas[3170]: segfault at 2aaab12f41c0 rip 2aaab12f41c0 rsp 7fffd9460408 error 4 I'm currently ar mythtv-0.20.1-161.fc7.x86_64 and kernel 2.6.22.1-33.fc7. If you need additonal information, please let me know. Wouter ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
Re: [ATrpms-users] mythfilldatabase segfaulting
Here is the output: $ gdb -x .gdbcmds /usr/bin/mythfilldatabase GNU gdb Red Hat Linux (6.6-15.fc7rh) Copyright (C) 2006 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 x86_64-redhat-linux-gnu... (no debugging symbols found) Using host libthread_db library /lib64/libthread_db.so.1. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496270416 (LWP 19949)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) illegal option: '-l' (use --help) Program exited with code 0374. (gdb) ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
Re: [ATrpms-users] mythfilldatabase segfaulting
Hi, I've had the same for a long time - a couple of weeks past I tried to do the debugging steps described on the mythtv-wiki, but as my hardware is a VIA processor, gdb fails mentioning something about floating-point registers missing :-( But perhaps you have more common hw. I do not think that it does any harm either, probably just a double free, but it's annoying to get error for each crontab run. My version is 0.20.1-157.fc7 Regards, Kim wouter lists wrote: Hi all, I have a freshly installed mythtv on a fresh fedora core 7. mythfilldatabase is always segfaulting: /usr/bin/mythfilldatabase --update --file 1 -1 /home/mythtv/jxmltv/xmltv.xml ... 2007-07-27 12:59:58.020 Connecting to backend server: 127.0.0.1:6543 (try 1 of 5) 2007-07-27 12:59:58.021 Using protocol version 31 2007-07-27 12:59:58.045 Received a remote 'Clear Cache' request 2007-07-27 12:59:58.069 mythfilldatabase run complete. Segmentation fault I don't think it's a big issue, as it already runs completely. More info: 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:19:58 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux # rpm -qa | grep myth mythtv-0.20.1-158.fc7.x86_64 mythcontrols-0.20.1-158.fc7.x86_64 mythnews-0.20.1-158.fc7.x86_64 mythtv-setup-0.20.1-158.fc7.x86_64 mythbrowser-0.20.1-158.fc7.x86_64 mythmusic-0.20.1-158.fc7.x86_64 mythvideo-0.20.1-158.fc7.x86_64 mythtv-suite-0.20.1-158.fc7.x86_64 mythtv-themes-0.20.1-158.fc7.x86_64 mythtv-frontend-0.20.1-158.fc7.x86_64 mythflix-0.20.1-158.fc7.x86_64 mytharchive-0.20.1-158.fc7.x86_64 mythweb-0.20.1-158.fc7.x86_64 libmyth-0.20.1-158.fc7.x86_64 mythphone-0.20.1-158.fc7.x86_64 mythgame-0.20.1-158.fc7.x86_64 myththemes-0.20.1-111.at.noarch mythplugins-0.20.1-158.fc7.x86_64 mythdvd-0.20.1-158.fc7.x86_64 mythweather-0.20.1-158.fc7.x86_64 mythgallery-0.20.1-158.fc7.x86_64 mythtv-backend-0.20.1-158.fc7.x86_64 regards, Wouter ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
Re: [ATrpms-users] mythfilldatabase segfaulting
On Fri, Jul 27, 2007 at 10:23:51PM +0200, wouter lists wrote: Hi all, I have a freshly installed mythtv on a fresh fedora core 7. mythfilldatabase is always segfaulting: /usr/bin/mythfilldatabase --update --file 1 -1 /home/mythtv/jxmltv/xmltv.xml ... 2007-07-27 12:59:58.020 Connecting to backend server: 127.0.0.1:6543 (try 1 of 5) 2007-07-27 12:59:58.021 Using protocol version 31 2007-07-27 12:59:58.045 Received a remote 'Clear Cache' request 2007-07-27 12:59:58.069 mythfilldatabase run complete. Segmentation fault I don't think it's a big issue, as it already runs completely. More info: 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:19:58 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux # rpm -qa | grep myth mythtv-0.20.1-158.fc7.x86_64 There were two updates since, maybe you could try them and see if this goes away. -- Axel.Thimm at ATrpms.net pgppBI9Z6lyiH.pgp Description: PGP signature ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users