#597 bzflag crashing with latest curl release

closed-fixed
libcurl (354)
8
2013-06-21
2006-07-16
Matthew Marshall
No

After upgrading to curl-5.15.4, bzflag will segfault
with the following backtrace:

(gdb) bt
#0 0x4004b94b in Curl_splay (i=1153071509, t=0x22)
at splay.c:68
#1 0x4004bab0 in Curl_splaygetbest (i=1153071509,
t=0x86dc4bc,
removed=0xbfe5f8d4) at splay.c:205
#2 0x40045e94 in curl_multi_perform
(multi_handle=0x83e25a0,
running_handles=0xbfe5f928) at multi.c:916
#3 0x0820fb91 in cURLManager::perform () at
cURLManager.cxx:291
#4 0x081558c9 in playingLoop () at playing.cxx:6099
#5 0x08157e31 in startPlaying (_display=0x8267468,
renderer=@0x8419fe8)
at playing.cxx:6735
#6 0x0812dd76 in main (argc=4, argv=0xbfe61384) at
bzflag.cxx:1286
(gdb)

Here is the bug for bzflag:
http://sourceforge.net/tracker/index.php?func=detail&aid=1522471&group_id=3248&atid=103248

Let me know if there is any more information I could
give that would be helpful.

MWM

Discussion

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

    Logged In: YES
    user_id=110526

    It's version is 7.15.4 and happens on debian/sid and archlinux.

    Udo

     
    • labels: 103860 --> libcurl
    • priority: 5 --> 8
     
  • Logged In: YES
    user_id=1144645

    Yup. That patch fixes the problem.

    MWM

     
  • Logged In: YES
    user_id=1110

    Thanks for verifying, that patch is now committed to CVS and
    will be part of the next curl release.

    Closing this report now.

     
    • status: open --> closed-fixed