Package: mame
Version: 0.148-1
Followup-For: Bug #679005
Now I have a little more info about the segfault:
Program received signal SIGSEGV, Segmentation fault.
0x0170029a in delegate_mfp::convert_to_generic(delegate_generic_class*) const
()
-- System Information:
Debian Release: 7.0
APT
Package: mame
Version: 0.148-1
Followup-For: Bug #679005
Hi!
I still have the segfault with an armhf build of 0.148-1.
Starting in gdb gives:
Program received signal SIGSEGV, Segmentation fault.
0x0170029a in ?? ()
If I only knew, what lib is in this memory range.
-- System Information:
Package: mame
Version: 0.146-5
Followup-For: Bug #679005
The problem still persists with the 146-5 package. This is all, that gdb shows,
as there are no debugging symbols:
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/arm-linux-gnueabihf/libthread_db.so.1.
Package: mame
Version: 0.146-1
Followup-For: Bug #679005
I am under Wheezy, which uses gcc-4.6.3, not 4.7.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
On Tue, Jun 26, 2012 at 05:36:44PM +0200, Thomas Maass wrote:
I am under Wheezy, which uses gcc-4.6.3, not 4.7.
Sure, but mame was compiled using gcc 4.7.
--
Jordi Mallach Pérez -- Debian developer http://www.debian.org/
jo...@sindominio.net jo...@debian.org
Package: mame
Version: 0.146-1
Severity: important
Hi!
I tried MAME on an armhf machine (Nvidia Tegra 2).
It segfaults there. I used video x11 and soft. The verbose
call shows, that mame.ini is parsed. After that there
is a segfault. Nothing to see with gdb, as there are
no debugging symbols.
On Mon, Jun 25, 2012 at 06:50:15PM +0200, Thomas Maass wrote:
I tried MAME on an armhf machine (Nvidia Tegra 2). It segfaults
there. I used video x11 and soft. The verbose call shows, that
mame.ini is parsed. After that there is a segfault. Nothing to see
with gdb, as there are no debugging
7 matches
Mail list logo
