XForms: Linux and Ctrl-C

From: Didier Verkindt (verkindt@lapp.in2p3.fr)
Date: Fri Nov 24 2000 - 09:52:39 EST

  • Next message: Jan Menzel: "Re: XForms: signal callback blocked by shortcut"

    # To subscribers of the xforms list from Didier Verkindt <verkindt@lapp.in2p3.fr> :

    Dear Xformers,

    Excuse me if the following question is not
    directly linked to an Xform problem, but I have seen
    that in Xform, there is a call to signal() function,
    and it is working under Linux ReadHat 6.2
    I made a code (without Xform) that calls also the function
    signal() to associate a handler to Ctrl-C signal (SIGINT)
    and under Linux, my code compile, runs but says "core dump"
    when I try Ctrl-C to stop it. Looking the core with gdb, I see
    the following:
    Core was generated by `../LINUX/Fbm fbm2.cfg 3'.
    Program terminated with signal 11, Erreur de segmentation.
    Reading symbols from /lib/libm.so.6...done.
    Reading symbols from /lib/libc.so.6...done.
    Reading symbols from /lib/ld-linux.so.2...done.
    Reading symbols from /lib/libnss_files.so.2...done.
    Reading symbols from /lib/libnss_nisplus.so.2...done.
    Reading symbols from /lib/libnsl.so.1...done.
    ---Type <return> to continue, or q <return> to quit---
    Reading symbols from /lib/libnss_nis.so.2...done.
    #0 0x4007c72a in _IO_vfprintf (s=0xbfffdff8, format=0x80933dc "%s: %s\n",
        at vfprintf.c:1259
    1259 vfprintf.c: Aucun fichier ou rpertoire de ce type.
    (gdb) where
    #0 0x4007c72a in _IO_vfprintf (s=0xbfffdff8, format=0x80933dc "%s: %s\n",
        at vfprintf.c:1259
    #1 0x400888e3 in _IO_vsprintf (string=0xbfffe0d0 "", format=0x80933dc
    "%s: %s\n", args=0xbfffe0c0)
        at iovsprintf.c:47
    #2 0x40082fbf in sprintf (s=0xbfffe0d0 "", format=0x80933dc "%s: %s\n")
    at sprintf.c:38
    #3 0x8067df2 in FdError ()
    #4 0x804bf91 in quitHandler ()
    #5 0x40054408 in __restore () at

    Does anyone already had such a problem?

    PS: I have an other code that uses shared memory. The producer
        that writes in shared memory seems to work perfectly
        under Linux, but the consumer, still under Linux of course,
        that reads from this shared memory
        returns NULL instead of the char array that should be read.
        This consumer works perfectly under OSF1.
        The address, under Linux, of the shared memory
        is 1078706176 (on HP Vectra 400 PC),
        while under OSF1 it is 8388608 (on a XP1000 workstation)
        Could this be the source of problem?

    Thank you.

     Didier Verkindt, CNRS, LAPP, Chemin de Bellevue,
                                   BP 110, 74941 ANNECY-LE-VIEUX, FRANCE
     tel: 33(0)450091628 fax: 33(0)450279495 email: verkindt@lapp.in2p3.fr
     web: http://wwwlapp.in2p3.fr/~verkindt

    To unsubscribe, send the message "unsubscribe" to
    xforms-request@bob.usuhs.mil or see
    XForms Home Page: http://world.std.com/~xforms
    List Archive: http://bob.usuhs.mil/mailserv/list-archives/

    This archive was generated by hypermail 2b29 : Fri Nov 24 2000 - 09:54:44 EST