[Qemu-devel] Bug with mpc8544ds machine.

[Frederic Konrad]

Hi everybody,

I didn't see anything on the list about that.
I get this bug in the current git.

I configured qemu with the following command line:

./configure --target-list=ppc-softmmu

I ran QEMU with the following command line:

./ppc-softmmu/qemu-system-ppc --M mpc8544ds

I get this segfault:

(gdb) bt
#0  0x00007fecf8e2a578 in qemu_input_transform_abs_rotate 
(evt=<optimized out>) at ui/input.c:79
#1  qemu_input_event_send (address@hidden, 
address@hidden) at ui/input.c:141
#2  0x00007fecf8e2a71a in qemu_input_event_send_key (src=0x0, 
key=<optimized out>, down=<optimized out>) at ui/input.c:185
#3  0x00007fecf8e2a7c2 in qemu_input_event_send_key_number 
(src=<optimized out>, num=<optimized out>, down=<optimized out>) at 
ui/input.c:195
#4  0x00007fecf8e26c9a in gd_key_event (widget=<optimized out>, 
key=<optimized out>, opaque=0x7fecfa790510) at ui/gtk.c:762
#5  0x00007fecf6864f0c in _gtk_marshal_BOOLEAN__BOXED () from 
/lib64/libgtk-x11-2.0.so.0
#6  0x00007fecf4f38910 in g_closure_invoke () from 
/lib64/libgobject-2.0.so.0
#7  0x00007fecf4f49d08 in signal_emit_unlocked_R () from 
/lib64/libgobject-2.0.so.0
#8  0x00007fecf4f518c7 in g_signal_emit_valist () from 
/lib64/libgobject-2.0.so.0
#9  0x00007fecf4f51de2 in g_signal_emit () from /lib64/libgobject-2.0.so.0
#10 0x00007fecf6998fee in gtk_widget_event_internal () from 
/lib64/libgtk-x11-2.0.so.0
#11 0x00007fecf69af96b in gtk_window_propagate_key_event () from 
/lib64/libgtk-x11-2.0.so.0
#12 0x00007fecf69af9af in gtk_window_key_release_event () from 
/lib64/libgtk-x11-2.0.so.0
#13 0x00007fecf6864f0c in _gtk_marshal_BOOLEAN__BOXED () from 
/lib64/libgtk-x11-2.0.so.0
#14 0x00007fecf4f38910 in g_closure_invoke () from 
/lib64/libgobject-2.0.so.0
#15 0x00007fecf4f49a80 in signal_emit_unlocked_R () from 
/lib64/libgobject-2.0.so.0
#16 0x00007fecf4f518c7 in g_signal_emit_valist () from 
/lib64/libgobject-2.0.so.0
#17 0x00007fecf4f51de2 in g_signal_emit () from /lib64/libgobject-2.0.so.0
#18 0x00007fecf6998fee in gtk_widget_event_internal () from 
/lib64/libgtk-x11-2.0.so.0
#19 0x00007fecf6862d67 in gtk_propagate_event () from 
/lib64/libgtk-x11-2.0.so.0
#20 0x00007fecf6863013 in gtk_main_do_event () from 
/lib64/libgtk-x11-2.0.so.0
#21 0x00007fecf64b9f1c in gdk_event_dispatch () from 
/lib64/libgdk-x11-2.0.so.0
#22 0x00007fecf80e0a55 in g_main_context_dispatch () from 
/lib64/libglib-2.0.so.0
#23 0x00007fecf8dc6958 in glib_pollfds_poll () at main-loop.c:190
#24 os_host_main_loop_wait (timeout=<optimized out>) at main-loop.c:235
#25 main_loop_wait (nonblocking=<optimized out>) at main-loop.c:484
#26 0x00007fecf8caeece in main_loop () at vl.c:2051
#27 main (argc=<optimized out>, argv=<optimized out>, envp=<optimized 
out>) at vl.c:4507

Git bisect gives:

9784e5793000f27cf4b506511fedf207dcf8521c is the first bad commit
commit 9784e5793000f27cf4b506511fedf207dcf8521c
Author: Gerd Hoffmann <address@hidden>
Date:   Wed Nov 27 11:59:25 2013 +0100

    input: keyboard: switch legacy handlers to new core

    legacy kbd event handlers are registered in the new core,
    so they receive events from the new input core code.
    keycode -> scancode translation needed here.

    legacy kbd_put_keycode() sends events to the new core.
    scancode -> keycode translation needed here.

    So with this patch the new input core is fully functional
    for keyboard events.  New + legacy interfaces can be mixed
    in any way.

    Signed-off-by: Gerd Hoffmann <address@hidden>

Did I miss something?

Thanks,
Fred