Mailing List Archive: MythTV: Dev

mythgame segmentation fault when mythgame binary is defined

Index | Next | Previous | View Threaded

tarek at tarek

Jan 12, 2003, 10:30 PM

Post #1 of 6 (835 views)
Permalink

mythgame segmentation fault when mythgame binary is defined

Hey guys!

I was wondering if anybody has experienced this..

the problem: mythgame seg. faults when executed from command line (and presumably when executed from mythfrontend though there is nothing said in that case) when *and only when* the myth game binary is defined properly.. I've heard some things about this in relation to scripts, however the xmame binary is not a script.. I don't really know, but it seems as though the problem has something to do with my libc.. upgrading to a higher version (i.e., 2.3) seems a nonoption, as it would require me to uninstall many, many packages..

Included below is a backtrace and an ls -l of my libc..

[root [at] courag orangey]# gdb mythgame
GNU gdb 5.2.1-2mdk (Mandrake Linux)
This GDB was configured as "i586-mandrake-linux-gnu"...
(gdb) run
Starting program: /usr/local/bin/mythgame

Program received signal SIGSEGV, Segmentation fault.
0x40965e4e in __strtol_internal () from /lib/i686/libc.so.6
Current language: auto; currently c
(gdb) backtrace
#0 0x40965e4e in __strtol_internal () from /lib/i686/libc.so.6
#1 0x40963757 in atoi () from /lib/i686/libc.so.6
#2 0x0805c775 in MameHandler::processGames() (this=0x80f5250)
at mamehandler.cpp:109
#3 0x0805bbba in GameHandler::processAllGames(MythContext*) (
context=0x80ddf50) at gamehandler.cpp:36
#4 0x0805afa1 in main (argc=1, argv=0xbffff6c4) at main.cpp:106
#5 0x40951082 in __libc_start_main () from /lib/i686/libc.so.6
(gdb) quit
The program is running. Exit anyway? (y or n) y
[root [at] courag orangey]# ls /lib/i686/
libc-2.2.5.so libm-2.2.5.so libpthread-0.9.so librt-2.2.5.so
libc.so.6 libm.so.6 libpthread.so.0 librt.so.1
[root [at] courag orangey]# ls /lib/i686/libc.so.6 -l
lrwxrwxrwx 1 root root 13 Jan 12 23:28
/lib/i686/libc.so.6 -> libc-2.2.5.so*

m0j0 at foofus

Jan 19, 2003, 10:52 AM

Post #2 of 6 (830 views)
Permalink

Re: mythgame segmentation fault when mythgame binary is defined [In reply to]

I'm having this exact same problem. Have you (or anyone else) figured
out a fix for it?

Thanks.

On Sun, 2003-01-12 at 23:30, Tarek Loubani wrote:
> Hey guys!
>
> I was wondering if anybody has experienced this..
>
> the problem: mythgame seg. faults when executed from command line (and presumably when executed from mythfrontend though there is nothing said in that case) when *and only when* the myth game binary is defined properly.. I've heard some things about this in relation to scripts, however the xmame binary is not a script.. I don't really know, but it seems as though the problem has something to do with my libc.. upgrading to a higher version (i.e., 2.3) seems a nonoption, as it would require me to uninstall many, many packages..
>
> Included below is a backtrace and an ls -l of my libc..
>
> [root [at] courag orangey]# gdb mythgame
> GNU gdb 5.2.1-2mdk (Mandrake Linux)
> This GDB was configured as "i586-mandrake-linux-gnu"...
> (gdb) run
> Starting program: /usr/local/bin/mythgame
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x40965e4e in __strtol_internal () from /lib/i686/libc.so.6
> Current language: auto; currently c
> (gdb) backtrace
> #0 0x40965e4e in __strtol_internal () from /lib/i686/libc.so.6
> #1 0x40963757 in atoi () from /lib/i686/libc.so.6
> #2 0x0805c775 in MameHandler::processGames() (this=0x80f5250)
> at mamehandler.cpp:109
> #3 0x0805bbba in GameHandler::processAllGames(MythContext*) (
> context=0x80ddf50) at gamehandler.cpp:36
> #4 0x0805afa1 in main (argc=1, argv=0xbffff6c4) at main.cpp:106
> #5 0x40951082 in __libc_start_main () from /lib/i686/libc.so.6
> (gdb) quit
> The program is running. Exit anyway? (y or n) y
> [root [at] courag orangey]# ls /lib/i686/
> libc-2.2.5.so libm-2.2.5.so libpthread-0.9.so librt-2.2.5.so
> libc.so.6 libm.so.6 libpthread.so.0 librt.so.1
> [root [at] courag orangey]# ls /lib/i686/libc.so.6 -l
> lrwxrwxrwx 1 root root 13 Jan 12 23:28
> /lib/i686/libc.so.6 -> libc-2.2.5.so*
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev [at] snowman
> http://www.snowman.net/mailman/listinfo/mythtv-dev

tarek at tarek

Jan 19, 2003, 11:22 AM

Post #3 of 6 (847 views)
Permalink

Re: mythgame segmentation fault when mythgame binary is defined [In reply to]

No sir.. OK, let's try to get some details going here and look for
similarities..

I'm running Mandrake 9.0 on an AMD/based system..
xmame version 0.61

what else are your specs?

tarek : )

>I'm having this exact same problem. Have you (or anyone else) figured
>out a fix for it?
>
>Thanks.
>
>
>
>On Sun, 2003-01-12 at 23:30, Tarek Loubani wrote:
> > Hey guys!
> >
> > I was wondering if anybody has experienced this..
> >
> > the problem: mythgame seg. faults when executed from command line (and
> presumably when executed from mythfrontend though there is nothing said
> in that case) when *and only when* the myth game binary is defined
> properly.. I've heard some things about this in relation to scripts,
> however the xmame binary is not a script.. I don't really know, but it
> seems as though the problem has something to do with my libc.. upgrading
> to a higher version (i.e., 2.3) seems a nonoption, as it would require me
> to uninstall many, many packages..
> >
> > Included below is a backtrace and an ls -l of my libc..
> >
> > [root [at] courag orangey]# gdb mythgame
> > GNU gdb 5.2.1-2mdk (Mandrake Linux)
> > This GDB was configured as "i586-mandrake-linux-gnu"...
> > (gdb) run
> > Starting program: /usr/local/bin/mythgame
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x40965e4e in __strtol_internal () from /lib/i686/libc.so.6
> > Current language: auto; currently c
> > (gdb) backtrace
> > #0 0x40965e4e in __strtol_internal () from /lib/i686/libc.so.6
> > #1 0x40963757 in atoi () from /lib/i686/libc.so.6
> > #2 0x0805c775 in MameHandler::processGames() (this=0x80f5250)
> > at mamehandler.cpp:109
> > #3 0x0805bbba in GameHandler::processAllGames(MythContext*) (
> > context=0x80ddf50) at gamehandler.cpp:36
> > #4 0x0805afa1 in main (argc=1, argv=0xbffff6c4) at main.cpp:106
> > #5 0x40951082 in __libc_start_main () from /lib/i686/libc.so.6
> > (gdb) quit
> > The program is running. Exit anyway? (y or n) y
> > [root [at] courag orangey]# ls /lib/i686/
> > libc-2.2.5.so libm-2.2.5.so libpthread-0.9.so librt-2.2.5.so
> > libc.so.6 libm.so.6 libpthread.so.0 librt.so.1
> > [root [at] courag orangey]# ls /lib/i686/libc.so.6 -l
> > lrwxrwxrwx 1 root root 13 Jan 12 23:28
> > /lib/i686/libc.so.6 -> libc-2.2.5.so*
> >
> > _______________________________________________
> > mythtv-dev mailing list
> > mythtv-dev [at] snowman
> > http://www.snowman.net/mailman/listinfo/mythtv-dev
>
>_______________________________________________
>mythtv-dev mailing list
>mythtv-dev [at] snowman
>http://www.snowman.net/mailman/listinfo/mythtv-dev

m0j0 at foofus

Jan 19, 2003, 11:23 AM

Post #4 of 6 (846 views)
Permalink

Re: mythgame segmentation fault when mythgame binary is defined [In reply to]

RedHat 7.3 (w/ 2.4.20) AMD XP 1800+
xmame (x11) 0.62.2

Xmame runs great if I call it directly. If mythgame has the correct
variable set for xmame, it segfaults immediately.

Is anyone else using mythgame from CVS successfully?

-j

On Sun, 2003-01-19 at 12:22, tarek Lubani wrote:
> No sir.. OK, let's try to get some details going here and look for
> similarities..
>
> I'm running Mandrake 9.0 on an AMD/based system..
> xmame version 0.61
>
> what else are your specs?
>
> tarek : )
>
> >I'm having this exact same problem. Have you (or anyone else) figured
> >out a fix for it?
> >
> >Thanks.
> >
> >
> >
> >On Sun, 2003-01-12 at 23:30, Tarek Loubani wrote:
> > > Hey guys!
> > >
> > > I was wondering if anybody has experienced this..
> > >
> > > the problem: mythgame seg. faults when executed from command line (and
> > presumably when executed from mythfrontend though there is nothing said
> > in that case) when *and only when* the myth game binary is defined
> > properly.. I've heard some things about this in relation to scripts,
> > however the xmame binary is not a script.. I don't really know, but it
> > seems as though the problem has something to do with my libc.. upgrading
> > to a higher version (i.e., 2.3) seems a nonoption, as it would require me
> > to uninstall many, many packages..
> > >
> > > Included below is a backtrace and an ls -l of my libc..
> > >
> > > [root [at] courag orangey]# gdb mythgame
> > > GNU gdb 5.2.1-2mdk (Mandrake Linux)
> > > This GDB was configured as "i586-mandrake-linux-gnu"...
> > > (gdb) run
> > > Starting program: /usr/local/bin/mythgame
> > >
> > > Program received signal SIGSEGV, Segmentation fault.
> > > 0x40965e4e in __strtol_internal () from /lib/i686/libc.so.6
> > > Current language: auto; currently c
> > > (gdb) backtrace
> > > #0 0x40965e4e in __strtol_internal () from /lib/i686/libc.so.6
> > > #1 0x40963757 in atoi () from /lib/i686/libc.so.6
> > > #2 0x0805c775 in MameHandler::processGames() (this=0x80f5250)
> > > at mamehandler.cpp:109
> > > #3 0x0805bbba in GameHandler::processAllGames(MythContext*) (
> > > context=0x80ddf50) at gamehandler.cpp:36
> > > #4 0x0805afa1 in main (argc=1, argv=0xbffff6c4) at main.cpp:106
> > > #5 0x40951082 in __libc_start_main () from /lib/i686/libc.so.6
> > > (gdb) quit
> > > The program is running. Exit anyway? (y or n) y
> > > [root [at] courag orangey]# ls /lib/i686/
> > > libc-2.2.5.so libm-2.2.5.so libpthread-0.9.so librt-2.2.5.so
> > > libc.so.6 libm.so.6 libpthread.so.0 librt.so.1
> > > [root [at] courag orangey]# ls /lib/i686/libc.so.6 -l
> > > lrwxrwxrwx 1 root root 13 Jan 12 23:28
> > > /lib/i686/libc.so.6 -> libc-2.2.5.so*
> > >
> > > _______________________________________________
> > > mythtv-dev mailing list
> > > mythtv-dev [at] snowman
> > > http://www.snowman.net/mailman/listinfo/mythtv-dev
> >
> >_______________________________________________
> >mythtv-dev mailing list
> >mythtv-dev [at] snowman
> >http://www.snowman.net/mailman/listinfo/mythtv-dev
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev [at] snowman
> http://www.snowman.net/mailman/listinfo/mythtv-dev
--
m0j0.j0j0 <m0j0 [at] foofus>
Foofus Networks

kedlm at knology

Jan 19, 2003, 11:53 AM

Post #5 of 6 (851 views)
Permalink

Re: mythgame segmentation fault when mythgame binary is defined [In reply to]

I am using the SDL version of xmame.

I had to comment out the screenshot dir lines in mamehandler.cpp I
think.

And use version 1.6 of main.cpp.

and then it worked fine.

The screenshot stuff is probably related to SDL version.

Not sure what those few 1.6 vs 1.7 changes did. Maybe moved the
mythgame db stuff to the backend? which for me is on another machine.

Mike

On Sun, 2003-01-19 at 13:23, m0j0.j0j0 wrote:
> RedHat 7.3 (w/ 2.4.20) AMD XP 1800+
> xmame (x11) 0.62.2
>
> Xmame runs great if I call it directly. If mythgame has the correct
> variable set for xmame, it segfaults immediately.
>
> Is anyone else using mythgame from CVS successfully?
>
> -j
>
>
> On Sun, 2003-01-19 at 12:22, tarek Lubani wrote:
> > No sir.. OK, let's try to get some details going here and look for
> > similarities..
> >
> > I'm running Mandrake 9.0 on an AMD/based system..
> > xmame version 0.61
> >
> > what else are your specs?
> >
> > tarek : )
> >
> > >I'm having this exact same problem. Have you (or anyone else) figured
> > >out a fix for it?
> > >
> > >Thanks.
> > >
> > >
> > >
> > >On Sun, 2003-01-12 at 23:30, Tarek Loubani wrote:
> > > > Hey guys!
> > > >
> > > > I was wondering if anybody has experienced this..
> > > >
> > > > the problem: mythgame seg. faults when executed from command line (and
> > > presumably when executed from mythfrontend though there is nothing said
> > > in that case) when *and only when* the myth game binary is defined
> > > properly.. I've heard some things about this in relation to scripts,
> > > however the xmame binary is not a script.. I don't really know, but it
> > > seems as though the problem has something to do with my libc.. upgrading
> > > to a higher version (i.e., 2.3) seems a nonoption, as it would require me
> > > to uninstall many, many packages..
> > > >
> > > > Included below is a backtrace and an ls -l of my libc..
> > > >
> > > > [root [at] courag orangey]# gdb mythgame
> > > > GNU gdb 5.2.1-2mdk (Mandrake Linux)
> > > > This GDB was configured as "i586-mandrake-linux-gnu"...
> > > > (gdb) run
> > > > Starting program: /usr/local/bin/mythgame
> > > >
> > > > Program received signal SIGSEGV, Segmentation fault.
> > > > 0x40965e4e in __strtol_internal () from /lib/i686/libc.so.6
> > > > Current language: auto; currently c
> > > > (gdb) backtrace
> > > > #0 0x40965e4e in __strtol_internal () from /lib/i686/libc.so.6
> > > > #1 0x40963757 in atoi () from /lib/i686/libc.so.6
> > > > #2 0x0805c775 in MameHandler::processGames() (this=0x80f5250)
> > > > at mamehandler.cpp:109
> > > > #3 0x0805bbba in GameHandler::processAllGames(MythContext*) (
> > > > context=0x80ddf50) at gamehandler.cpp:36
> > > > #4 0x0805afa1 in main (argc=1, argv=0xbffff6c4) at main.cpp:106
> > > > #5 0x40951082 in __libc_start_main () from /lib/i686/libc.so.6
> > > > (gdb) quit
> > > > The program is running. Exit anyway? (y or n) y
> > > > [root [at] courag orangey]# ls /lib/i686/
> > > > libc-2.2.5.so libm-2.2.5.so libpthread-0.9.so librt-2.2.5.so
> > > > libc.so.6 libm.so.6 libpthread.so.0 librt.so.1
> > > > [root [at] courag orangey]# ls /lib/i686/libc.so.6 -l
> > > > lrwxrwxrwx 1 root root 13 Jan 12 23:28
> > > > /lib/i686/libc.so.6 -> libc-2.2.5.so*
> > > >
> > > > _______________________________________________
> > > > mythtv-dev mailing list
> > > > mythtv-dev [at] snowman
> > > > http://www.snowman.net/mailman/listinfo/mythtv-dev
> > >
> > >_______________________________________________
> > >mythtv-dev mailing list
> > >mythtv-dev [at] snowman
> > >http://www.snowman.net/mailman/listinfo/mythtv-dev
> >
> > _______________________________________________
> > mythtv-dev mailing list
> > mythtv-dev [at] snowman
> > http://www.snowman.net/mailman/listinfo/mythtv-dev
--
Michael Kedl <kedlm [at] knology>

mjw at woogie

Jan 19, 2003, 2:31 PM

Post #6 of 6 (838 views)
Permalink

Re: mythgame segmentation fault when mythgame binary is defined [In reply to]

That's funny, I was in the middle of composing an email on this very
topic when I got your first message. I'm having this problem, too.
I've tried it on 2 different boxes, a P-III 1 GHz running RedHat 8.0
with kernel 2.4.18-17.8.0 (gotta love RH) and a P-4 2.0 GHz running
RedHat 7.3 with kernel 2.4.18-10. Both are running mythgame from CVS
that I checked out yesterday, and xmame 0.62.2.

Woogie

m0j0.j0j0 wrote:

>RedHat 7.3 (w/ 2.4.20) AMD XP 1800+
>xmame (x11) 0.62.2
>
>Xmame runs great if I call it directly. If mythgame has the correct
>variable set for xmame, it segfaults immediately.
>
>Is anyone else using mythgame from CVS successfully?
>
>-j
>
>
>On Sun, 2003-01-19 at 12:22, tarek Lubani wrote:
>
>
>>No sir.. OK, let's try to get some details going here and look for
>>similarities..
>>
>>I'm running Mandrake 9.0 on an AMD/based system..
>>xmame version 0.61
>>
>>what else are your specs?
>>
>>tarek : )
>>
>>
>>
>>>I'm having this exact same problem. Have you (or anyone else) figured
>>>out a fix for it?
>>>
>>>Thanks.
>>>
>>>
>>>
>>>On Sun, 2003-01-12 at 23:30, Tarek Loubani wrote:
>>>
>>>
>>>>Hey guys!
>>>>
>>>>I was wondering if anybody has experienced this..
>>>>
>>>>the problem: mythgame seg. faults when executed from command line (and
>>>>
>>>>
>>>presumably when executed from mythfrontend though there is nothing said
>>>in that case) when *and only when* the myth game binary is defined
>>>properly.. I've heard some things about this in relation to scripts,
>>>however the xmame binary is not a script.. I don't really know, but it
>>>seems as though the problem has something to do with my libc.. upgrading
>>>to a higher version (i.e., 2.3) seems a nonoption, as it would require me
>>>to uninstall many, many packages..
>>>
>>>
>>>>Included below is a backtrace and an ls -l of my libc..
>>>>
>>>>[root [at] courag orangey]# gdb mythgame
>>>>GNU gdb 5.2.1-2mdk (Mandrake Linux)
>>>>This GDB was configured as "i586-mandrake-linux-gnu"...
>>>>(gdb) run
>>>>Starting program: /usr/local/bin/mythgame
>>>>
>>>>Program received signal SIGSEGV, Segmentation fault.
>>>>0x40965e4e in __strtol_internal () from /lib/i686/libc.so.6
>>>>Current language: auto; currently c
>>>>(gdb) backtrace
>>>>#0 0x40965e4e in __strtol_internal () from /lib/i686/libc.so.6
>>>>#1 0x40963757 in atoi () from /lib/i686/libc.so.6
>>>>#2 0x0805c775 in MameHandler::processGames() (this=0x80f5250)
>>>> at mamehandler.cpp:109
>>>>#3 0x0805bbba in GameHandler::processAllGames(MythContext*) (
>>>> context=0x80ddf50) at gamehandler.cpp:36
>>>>#4 0x0805afa1 in main (argc=1, argv=0xbffff6c4) at main.cpp:106
>>>>#5 0x40951082 in __libc_start_main () from /lib/i686/libc.so.6
>>>>(gdb) quit
>>>>The program is running. Exit anyway? (y or n) y
>>>>[root [at] courag orangey]# ls /lib/i686/
>>>>libc-2.2.5.so libm-2.2.5.so libpthread-0.9.so librt-2.2.5.so
>>>>libc.so.6 libm.so.6 libpthread.so.0 librt.so.1
>>>>[root [at] courag orangey]# ls /lib/i686/libc.so.6 -l
>>>>lrwxrwxrwx 1 root root 13 Jan 12 23:28
>>>>/lib/i686/libc.so.6 -> libc-2.2.5.so*
>>>>
>>>>_______________________________________________
>>>>mythtv-dev mailing list
>>>>mythtv-dev [at] snowman
>>>>http://www.snowman.net/mailman/listinfo/mythtv-dev
>>>>
>>>>
>>>_______________________________________________
>>>mythtv-dev mailing list
>>>mythtv-dev [at] snowman
>>>http://www.snowman.net/mailman/listinfo/mythtv-dev
>>>
>>>
>>_______________________________________________
>>mythtv-dev mailing list
>>mythtv-dev [at] snowman
>>http://www.snowman.net/mailman/listinfo/mythtv-dev
>>
>>

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads