#457 client fails with segv when joining a server (sometimes)

closed-works-for-me
nobody
BZFlag (350)
7
2008-03-21
2006-07-14
Udo Müller
No

Perhaps same as #1510999

bzflag (2.0.8.20060605, Debian Sid, dist-upgrade today)
fails with segv.
The first start works fine, all other segv.

All other open gl applications work fine. Behaviour is
independent from used x.org driver (ati, radeon, fglrx).

Used hardware:

mueller@mueller:~$ lspci
00:00.0 Host bridge: Intel Corporation 82855PM
Processor to I/O Controller (rev 21)
00:01.0 PCI bridge: Intel Corporation 82855PM Processor
to AGP Controller (rev 21)
00:1d.0 USB Controller: Intel Corporation
82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI
Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation
82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI
Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation
82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI
Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM
(ICH4/ICH4-M) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI
Bridge (rev 83)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M)
LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801DBM
(ICH4-M) IDE Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corporation
82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio
Controller (rev 03)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc
RV350 [Mobility Radeon 9600 M10]
02:00.0 Ethernet controller: Realtek Semiconductor Co.,
Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ac)
02:01.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ac)
02:01.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE
1394 Controller (rev 04)
02:02.0 Network controller: Intel Corporation
PRO/Wireless 2200BG Network Connection (rev 05)

If you need further information please contact me.

Udo

Discussion

  • Udo Müller
    Udo Müller
    2006-07-14

    2 strace logs: first from successful start, second from fail

     
    Attachments
  • Udo Müller
    Udo Müller
    2006-07-14

    • labels: --> BZFlag
    • priority: 5 --> 7
     
  • Logged In: YES
    user_id=1144645

    I seem to have the same problem, only for me, it only
    happens when I join a server without first going to
    the 'find server' page. (Is this your behavior?)

    I'm on archlinux, and it seemed to have started after a
    package update, although I have no idea which package. It
    also started happening for my brother (also on archlinux)
    at the same time. So, it seems to be a dependency
    problem; nothing with the hardware.

    Here's the bt:
    #0 0x4036f43a in Curl_splay () from /usr/lib/libcurl.so.3
    #1 0x4036f570 in Curl_splaygetbest ()
    from /usr/lib/libcurl.so.3
    #2 0x40369a34 in curl_multi_perform ()
    from /usr/lib/libcurl.so.3
    #3 0x0820fb91 in cURLManager::perform () at
    cURLManager.cxx:291
    #4 0x081558c9 in playingLoop () at playing.cxx:6099
    #5 0x08157e31 in startPlaying (_display=0x8267388,
    renderer=@0x84197b8)
    at playing.cxx:6735
    #6 0x0812dd76 in main (argc=2, argv=0xbfb268a4) at
    bzflag.cxx:1286

    MWM

     
  • Udo Müller
    Udo Müller
    2006-07-14

    Logged In: YES
    user_id=110526

    mmarschall: You are right. If i use "find server" first i
    can join any server i want. It only happens when joining a
    server without searching and choosing first.

    Same here with a package upgrade: It wasnt a bzflag update.
    It must have been a lib or sth.

    Udo

     
  • Sean Morrison
    Sean Morrison
    2006-07-15

    Logged In: YES
    user_id=785737

    The crash is caused by a very recent update to libcurl on Debian/Ubuntu (about
    three or four weeks ago) hence why Curl functions show up in the backtrace.
    The problem is looking to be a bonefide bug of the libcurl update, not
    something that BZFlag is doing incorrectly. As far as has been shown, this only
    affects those using that very latest libcurl update. You can avoid the problem by
    either downgrading to an earlier version of libcurl or compiling an earlier version
    yourself. The bug should be reported to the libcurl package, I've not heard that
    anyone has taken the initiative to do so.

     
  • Jeff Myers
    Jeff Myers
    2008-03-21

    • status: open --> closed-works-for-me