Networking

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • help needed for debugging segfault

    5 answers - 772 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    Hello,
    I've been banging my head against this for a few days.
    I've installed freeradius 1.1.0 from cvs and I'm doing EAP-PEAP using
    ntlm_auth for authentication. freeradius segfaults while sending the
    access-accept packet.
    In my first post someone instructed me to enable coredumps in freeradius
    and post the result.
    I've compiled freeradius using , set allow_core_dumps
    = yes in radiusd.conf and used ulimit to remove coredump filesize limit
    from my shell, but it seems freeradius still doesn't dump core.
    The radius server is a Debian testing box. The Wi-Fi accesspoint is a
    D-Link DWL-2100AP.
    Is there anything else I can do? Is this a freeradius issue or an S
    issue?
    thanks
  • No.1 | | 481 bytes | |

    Luca Corti wrote:

    I've compiled freeradius using , set allow_core_dumps
    = yes in radiusd.conf and used ulimit to remove coredump filesize limit
    from my shell, but it seems freeradius still doesn't dump core.

    If there is no coredump to be found, you could try to run FreeRADIUS
    directly from gdb.

    $ gdb /usr/sbin/freeradius

    (gdb) run -X

    You could also try to run FreeRADIUS in valgrind.

    $ valgrind /usr/sbin/freeradius -X
  • No.2 | | 940 bytes | |

    hi

    I've installed freeradius 1.1.0 from cvs and I'm doing EAP-PEAP using
    ntlm_auth for authentication. freeradius segfaults while sending the
    access-accept packet.

    In my first post someone instructed me to enable coredumps in
    freeradius
    and post the result.

    just a thought - wouldn't it be principally the same to run
    freeradius in the gdb and to backtrace (bt) after gdb catches sigsegv?

    ciao
    artur

    I've compiled freeradius using , set
    allow_core_dumps
    = yes in radiusd.conf and used ulimit to remove coredump filesize
    limit
    from my shell, but it seems freeradius still doesn't dump core.

    The radius server is a Debian testing box. The Wi-Fi accesspoint is a
    D-Link DWL-2100AP.

    Is there anything else I can do? Is this a freeradius issue or an S
    issue?
    --
    thanks

    -
    List info/subscribe/unsubscribe? See
  • No.3 | | 966 bytes | |

    Luca Corti wrote:
    Hello,

    I've been banging my head against this for a few days.

    I've installed freeradius 1.1.0 from cvs and I'm doing EAP-PEAP using
    ntlm_auth for authentication. freeradius segfaults while sending the
    access-accept packet.

    In my first post someone instructed me to enable coredumps in freeradius
    and post the result.

    I've compiled freeradius using , set allow_core_dumps
    = yes in radiusd.conf and used ulimit to remove coredump filesize limit
    from my shell, but it seems freeradius still doesn't dump core.

    The radius server is a Debian testing box. The Wi-Fi accesspoint is a
    D-Link DWL-2100AP.

    Is there anything else I can do? Is this a freeradius issue or an S
    issue?

    thanks

    Try checking if the server runs with different user/groups, disable that.

    Worked to an extent for me.
    -
    List info/subscribe/unsubscribe? See
  • No.4 | | 1515 bytes | |

    Artur Hecker wrote:
    hi
    >
    >
    >I've installed freeradius 1.1.0 from cvs and I'm doing EAP-PEAP using
    >ntlm_auth for authentication. freeradius segfaults while sending the
    >access-accept packet.
    >>

    >In my first post someone instructed me to enable coredumps in
    >freeradius
    >and post the result.
    >

    just a thought - wouldn't it be principally the same to run
    freeradius in the gdb and to backtrace (bt) after gdb catches sigsegv?
    I suppose, I have reported the same problem a few minutes ago. I ran
    radiusd under gdb and put the backtrace at
    The configuration files are in the
    same directory.

    Norbert

    ciao
    artur
    >
    >
    >I've compiled freeradius using , set allow_core_dumps
    >= yes in radiusd.conf and used ulimit to remove coredump filesize limit
    >from my shell, but it seems freeradius still doesn't dump core.
    >>

    >The radius server is a Debian testing box. The Wi-Fi accesspoint is a
    >D-Link DWL-2100AP.
    >>

    >Is there anything else I can do? Is this a freeradius issue or an S
    >issue?
    >>
    >>

    >thanks
    >>

    - List info/subscribe/unsubscribe? See

    -
    List info/subscribe/unsubscribe? See
  • No.5 | | 639 bytes | |

    Tue, 2005-11-22 at 14:49 +0100, Norbert Wegener wrote:

    Managed to run freeradius under gdb, same happening here.

    modcall: leaving group authenticate (returns ok) for request 8
    Sending Access-Accept of id 9 to 1.2.3.4 port 1025
    MS-MPPE-Recv-Key =

    Program received signal SIGSEGV, Segmentation fault.
    [Switching to Thread -1212503840 (LWP 25694)]
    0xb7c3312d in memset () from /lib/tls/libc.so.6
    (gdb) bt
    #0 0xb7c3312d in memset () from /lib/tls/libc.so.6
    #1 0xb7f51e98 in rad_vp2attr (packet=0x0, original=0x0, secret=0x0,
    vp=0x0, ptr=0x0) at radius.c:484
    #2 0x00000000 in ? ()

    thanks

Re: help needed for debugging segfault


max 4000 letters.
Your nickname that display:
In order to stop the spam: 5 + 4 =
QUESTION ON "Networking"

EMSDN.COM