All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Taimoor Mirza <taimoor.mrza@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] stack smash while using SDL 1.2.5 with QEMU 2.9
Date: Wed, 06 Sep 2017 08:28:44 +0200	[thread overview]
Message-ID: <87tw0ge3xf.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAO6-N=a7WwhsDqZsm=wppXWMunGub=RH17FBk5w_tK0vu-8=cQ@mail.gmail.com> (Taimoor Mirza's message of "Mon, 21 Aug 2017 18:02:07 +0500")

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

  reply	other threads:[~2017-09-06  6:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2017-09-06  7:20   ` Gerd Hoffmann
2017-09-06  7:01 ` Thomas Huth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tw0ge3xf.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=taimoor.mrza@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.