* [Qemu-devel] stack smash while using SDL 1.2.5 with QEMU 2.9
@ 2017-08-21 13:02 Taimoor Mirza
2017-09-06 6:28 ` Markus Armbruster
2017-09-06 7:01 ` Thomas Huth
0 siblings, 2 replies; 4+ messages in thread
From: Taimoor Mirza @ 2017-08-21 13:02 UTC (permalink / raw)
To: qemu-devel
Hi Guys,
I have been using QEMU 1.5 earlier with SDL version 1.2.5. Now we have
decided to move to new version of QEMU. I have built QEMU binaries with SDL
support using SDL 1.2.5 that we were using earlier. Windows binaries work
fine but I get stack smash in sdl.c on Linux. Below are stack traces that I
have got from GDB:
Program received signal SIGABRT, Aborted.
0x00007ffff6e74c37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x00007ffff6e74c37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x00007ffff6e78028 in __GI_abort () at abort.c:89
#2 0x00007ffff6eb12a4 in __libc_message (do_abort=do_abort@entry=1,
fmt=fmt@entry=0x7ffff6fc0d70 "*** %s ***: %s terminated\n") at
../sysdeps/posix/libc_fatal.c:175
#3 0x00007ffff6f4c83c in __GI___fortify_fail (msg=<optimized out>,
msg@entry=0x7ffff6fc0d58 "stack smashing detected") at fortify_fail.c:38
#4 0x00007ffff6f4c7e0 in __stack_chk_fail () at stack_chk_fail.c:28
#5 0x0000555555a66909 in sdl_display_init (ds=<optimized out>,
full_screen=0, no_frame=<optimized out>) at
/scratch/tmirza/builds/qemu_build/obj/qemu-src-master-999999-arm-linux-gnueabi-x86_64-linux-gnu/ui/sdl.c:1054
#6 0x0000000006e00002 in ?? ()
#7 0x0000000006e00003 in ?? ()
#8 0x0000555556feca30 in ?? ()
#9 0x0000555555c784e1 in ?? ()
#10 0x0000000000000000 in ?? ()
I want to know whether it is a known issue and Is QEMU 2.9 compatible with
SDL 1.2.5?
Thanks,
Taimoor Mirza
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] stack smash while using SDL 1.2.5 with QEMU 2.9
2017-08-21 13:02 [Qemu-devel] stack smash while using SDL 1.2.5 with QEMU 2.9 Taimoor Mirza
@ 2017-09-06 6:28 ` Markus Armbruster
2017-09-06 7:20 ` Gerd Hoffmann
2017-09-06 7:01 ` Thomas Huth
1 sibling, 1 reply; 4+ messages in thread
From: Markus Armbruster @ 2017-09-06 6:28 UTC (permalink / raw)
To: Taimoor Mirza; +Cc: qemu-devel, Gerd Hoffmann
Gerd, any ideas?
Taimoor Mirza <taimoor.mrza@gmail.com> writes:
> Hi Guys,
>
> I have been using QEMU 1.5 earlier with SDL version 1.2.5. Now we have
> decided to move to new version of QEMU. I have built QEMU binaries with SDL
> support using SDL 1.2.5 that we were using earlier. Windows binaries work
> fine but I get stack smash in sdl.c on Linux. Below are stack traces that I
> have got from GDB:
>
> Program received signal SIGABRT, Aborted.
> 0x00007ffff6e74c37 in __GI_raise (sig=sig@entry=6) at
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
> (gdb) bt
> #0 0x00007ffff6e74c37 in __GI_raise (sig=sig@entry=6) at
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #1 0x00007ffff6e78028 in __GI_abort () at abort.c:89
> #2 0x00007ffff6eb12a4 in __libc_message (do_abort=do_abort@entry=1,
> fmt=fmt@entry=0x7ffff6fc0d70 "*** %s ***: %s terminated\n") at
> ../sysdeps/posix/libc_fatal.c:175
> #3 0x00007ffff6f4c83c in __GI___fortify_fail (msg=<optimized out>,
> msg@entry=0x7ffff6fc0d58 "stack smashing detected") at fortify_fail.c:38
> #4 0x00007ffff6f4c7e0 in __stack_chk_fail () at stack_chk_fail.c:28
> #5 0x0000555555a66909 in sdl_display_init (ds=<optimized out>,
> full_screen=0, no_frame=<optimized out>) at
> /scratch/tmirza/builds/qemu_build/obj/qemu-src-master-999999-arm-linux-gnueabi-x86_64-linux-gnu/ui/sdl.c:1054
> #6 0x0000000006e00002 in ?? ()
> #7 0x0000000006e00003 in ?? ()
> #8 0x0000555556feca30 in ?? ()
> #9 0x0000555555c784e1 in ?? ()
> #10 0x0000000000000000 in ?? ()
>
> I want to know whether it is a known issue and Is QEMU 2.9 compatible with
> SDL 1.2.5?
>
> Thanks,
> Taimoor Mirza
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] stack smash while using SDL 1.2.5 with QEMU 2.9
2017-08-21 13:02 [Qemu-devel] stack smash while using SDL 1.2.5 with QEMU 2.9 Taimoor Mirza
2017-09-06 6:28 ` Markus Armbruster
@ 2017-09-06 7:01 ` Thomas Huth
1 sibling, 0 replies; 4+ messages in thread
From: Thomas Huth @ 2017-09-06 7:01 UTC (permalink / raw)
To: Taimoor Mirza, qemu-devel
On 21.08.2017 15:02, Taimoor Mirza wrote:
> Hi Guys,
>
> I have been using QEMU 1.5 earlier with SDL version 1.2.5. Now we have
> decided to move to new version of QEMU. I have built QEMU binaries with SDL
> support using SDL 1.2.5 that we were using earlier.
SDL 1.2.5 is incredibly old - it has been released 2002. Could you
please try with a newer version instead (i.e. version 1.2.15 from 2012,
or even upgrade to SDL2)?
Thomas
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] stack smash while using SDL 1.2.5 with QEMU 2.9
2017-09-06 6:28 ` Markus Armbruster
@ 2017-09-06 7:20 ` Gerd Hoffmann
0 siblings, 0 replies; 4+ messages in thread
From: Gerd Hoffmann @ 2017-09-06 7:20 UTC (permalink / raw)
To: Markus Armbruster, Taimoor Mirza; +Cc: qemu-devel
On Wed, 2017-09-06 at 08:28 +0200, Markus Armbruster wrote:
> Gerd, any ideas?
> > I want to know whether it is a known issue and Is QEMU 2.9
> > compatible with
> > SDL 1.2.5?
Everything working fine here, even valgrind doesn't report anything
unusual.
qemu 2.10, SDL 1.2.15
Do you really use SDL 1.2.5 not 1.2.15?
If so I'd strongly suggest to update SDL.
cheers,
Gerd
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-09-06 7:20 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-08-21 13:02 [Qemu-devel] stack smash while using SDL 1.2.5 with QEMU 2.9 Taimoor Mirza
2017-09-06 6:28 ` Markus Armbruster
2017-09-06 7:20 ` Gerd Hoffmann
2017-09-06 7:01 ` Thomas Huth
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).