[mythtv] issue with version 0.18 -- x86_64

[RKVJ]

Hello Myth-Dev,

I'm trying to install mythtv on AMD64/fedora4 machine,
using a pre-compiled mythtv-suite. I get segmentation
fault when trying to run mythfrontend. I came across a
post on the packager's mailing list, where a user had
experienced similar problems, with mythtv - version
0.17, even when installed using svn. An svn-update
seems to have been the solution. The post was dated
about a month ago and I attach it below. Since I see
the same problem with the stable 0.18 version of
mythtv, I'm wondering if the fixes for x86_64 have
been released to the stable version??

Thanks

RKVJ

------related post from ATRPMS mailing list-----

[ATrpms-users] Re: X86_64 FC4 Segmentation Fault

Axel,

Thanks for your response.

Yesterday the problem was fixed after I did a svn up.

I could use successfully mythtv on my
AMD64/Hauppauge350, yeah!

alex.

Axel Thimm wrote:

>On Sun, Sep 25, 2005 at 09:07:31PM -0700, Alexandre
Parenteau wrote:
>  
>
>>Hi,
>>
>>I am a new user, and I had the same problem (I used
the RPM ar first). I
>>went as far as compiling mythtv directly from svn,
and I get the same
>>problem at start-up, something with threads being
spawned (?):
>>    
>>
>
>Yes, that looks like a thread problem, but probably
not related to the
>other reported problems.
>
>Since even svn shows this, I would report it to the
mythtv
>lists. Unfortunatley most developers don't use mythtv
on 64 bits, so
>some issues slip in.
>
>BTW you can use the 32 bit variant of mythtv until
this is fixed.
>
>  
>
>>>/usr/local/bin/mythfrontend
>>>      
>>>
>>2005-09-25 20:56:20.149 Using runtime prefix =
/usr/local
>>Detaching after fork from child process 7377.
>>(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)
>>2005-09-25 20:56:21.617 New DB connection, total: 1
>>2005-09-25 20:56:21.622 Total desktop dim:
1280x1024, with 1 screen[s].
>>2005-09-25 20:56:21.624 Using screen 0, 1280x1024 at
0,0
>>[New Thread 1084229984 (LWP 7380)]
>>
>>Program received signal SIG33, Real-time event 33.
>>[Switching to Thread 1084229984 (LWP 7380)]
>>0x00002aaaae05e8f2 in clone () from /lib64/libc.so.6
>>(gdb) thread
>>[Current thread is 2 (Thread 1084229984 (LWP 7380))]
>>(gdb) thread 1
>>[Switching to thread 1 (Thread 46912561695648 (LWP
7374))]#0
>>0x00002aaaad9f182a in __nptl_setxid ()
>>from /lib64/libpthread.so.0
>>(gdb) bt
>>#0 0x00002aaaad9f182a in __nptl_setxid () from
/lib64/libpthread.so.0
>>#1 0x00002aaaae028107 in setuid () from
/lib64/libc.so.6
>>#2 0x000000000042638a in ?? ()
>>#3 0x00002aaaadfb13cf in __libc_start_main () from
/lib64/libc.so.6
>>#4 0x000000000041f8b9 in ?? ()
>>#5 0x00007fffff804e98 in ?? ()
>>#6 0x0000000000000000 in ?? ()
>>(gdb) thread 2
>>[Switching to thread 2 (Thread 1084229984 (LWP
7380))]#0 0x00002aaaae05e8f2
>>in clone () from /lib64/libc.so.6
>>(gdb) bt
>>#0 0x00002aaaae05e8f2 in clone () from
/lib64/libc.so.6
>>#1 0x00002aaaad9f28f0 in __make_stacks_executable ()
from
>>/lib64/libpthread.so.0
>>#2 0x0000000040a00960 in ?? ()
>>#3 0x0000000000000000 in ?? ()
>>
>>Thanks,
>>alex.
>>    
>>
>
>  
>
>>_______________________________________________




	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com