[AD] [ alleg-Bugs-3556662 ] init_console segfaults during exit(0) after fork

[SourceForge.net <noreply@xxxxxxxxxx>]

Bugs item #3556662, was opened at 2012-08-12 06:13
Message generated for change (Tracker Item Submitted) made by tobi_v
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105665&aid=3556662&group_id=5665

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Linux
Group: 4.4
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Tobi Vollebregt (tobi_v)
Assigned to: Nobody/Anonymous (nobody)
Summary: init_console segfaults during exit(0) after fork

Initial Comment:
I'm trying to use Allegro 4.4 on an embedded platform (ea3250 development board), using the Linux console and fbcon subsystems.

I found that a segmentation fault in ldlinux.so is triggered in the parent process after the fork in init_console (src/linux/lconsole.c) if install_keyboard is not called before set_gfx_mode. Unfortunately the trace is useless, and valgrind (from debian testing) doesn't work yet on ARM.

    Allegro application is running on VT 2

    Program received signal SIGSEGV, Segmentation fault.
    0x40009cc4 in ?? () from /lib/ld-linux.so.3
    (gdb) bt
    #0  0x40009cc4 in ?? () from /lib/ld-linux.so.3
    #1  0x4000a45c in ?? () from /lib/ld-linux.so.3
    #2  0x4000eb18 in ?? () from /lib/ld-linux.so.3
    #3  0x40014d54 in ?? () from /lib/ld-linux.so.3
    #4  0x00000000 in ?? ()

If install_keyboard is called before set_gfx_mode, no segmentation fault occurs. This leads me to believe the fbcon or linux console subsystem incorrectly assume install_keyboard has been called before.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105665&aid=3556662&group_id=5665