Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#4950 - Latest curl causes bzflag to segfault
Attached to Project:
Arch Linux
Opened by Michal Witkowski (Neuro) - Monday, 03 July 2006, 13:10 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 04 July 2006, 07:25 GMT
Opened by Michal Witkowski (Neuro) - Monday, 03 July 2006, 13:10 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 04 July 2006, 07:25 GMT
|
DetailsAfter today's update to testing/current bzflag started segfaulting upon map downloads. After running gdb it appears that it's caused by libcurl.so.3:
gdb bzflag GNU gdb 6.5 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"...(no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/bzflag (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1224440112 (LWP 2791)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New Thread -1233212512 (LWP 2795)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1224440112 (LWP 2791)] 0xb7bf8580 in Curl_splaygetbest () from /usr/lib/libcurl.so.3 (gdb) quit I've got the latest package: Name : curl Version : 7.15.4-1 Packager : Tobias Powalowski <tpowa@archlinux.org> Build Date : Sat Jul 1 12:13:12 2006 UTC Install Date : Mon Jul 3 08:59:26 2006 UTC Reason: : installed as a dependency for another package Depends On : bash openssl zlib Required By : bzflag gnupg vorbis-tools xine-ui This causes bzflag from package bzflag-2.0.8-2 to segfault. The problem also accured after I compiled my own bzflag package against the newest curl package. Everything worked fine before the latest curl update. |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 13 August 2006, 14:56 GMT
Reason for closing: Fixed
Additional comments about closing: Curl 7.15.5 has been released which contains the quoted fix.
Sunday, 13 August 2006, 14:56 GMT
Reason for closing: Fixed
Additional comments about closing: Curl 7.15.5 has been released which contains the quoted fix.
I don't know what is going on here exactly, so I'll watch the debian bug a bit more closely.
Until then it seems the only way for bzflag not to segfault is to use the old package curl-7.15.3-1.
Daniel (17 July 2006)
- Jari Sundell did some excellent research and bug tracking, figured out that
we did wrong and patched it: When nodes were removed from the splay tree,
and we didn't properly remove it from the splay tree when an easy handle was
removed from a multi stack and thus we could wrongly leave a node in the
splay tree pointing to (bad) memory.
Now to find out which files were affected.