GNOME Bugzilla – Bug 161406
bug in http-neon-method.c
Last modified: 2005-01-30 19:02:39 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: gnome-utils Severity: normal Version: GNOME2.8.0 2.2.4 Gnome-Distributor: Red Hat, Inc Synopsis: balsa crashes when making an attachment Bugzilla-Product: gnome-utils Bugzilla-Component: gdict Bugzilla-Version: 2.2.4 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: see summary Steps to reproduce the crash: 1. compose mail 2. attach a pdf file from home directory 3. Expected Results: kaboom How often does this happen? every time Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/balsa' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -151193376 (LWP 4925)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x007da7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 53569
Thread 1 (Thread -151193376 (LWP 4925))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-15 15:04 ------- Unknown version 2.2.4 in product gnome-utils. Setting version to "2.2.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-utils". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was flafon@mac.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Appears to be a unique stack trace, according to the simple-dup-finder. Reassigning to balsa.
Thanks for the report! To help track this down, could you provide your Balsa version and gnome-vfs-2.0 version?
From mail: "Balsa 2.2.4. I figured out the problem. If the file name has http characters in it like %20 then it explodes. Gnome is 2.8.0" I think this was mentioned on gnome-vfs-list and is probably a bug in the new http method. From that mail: "> $ gnomevfs-ls http://superbeast.ucsd.edu/~landry/ArX/wlandry/arx/2/1/,cache/ > arx.2.1,59.tar.gz (Regular, application/x-tar) size 784886mode 0000 > $ gnomevfs-ls http://superbeast.ucsd.edu/~landry/ArX/wlandry/arx/2/1/%2Ccache/ > Segmentation fault bug in http-neon-method.c [I tested with gnome-vfs 2.8.3] (HEAD doesnt have http-neon-method.c anymore) function do_open_directory pfctx... propfind context by default pfctx->* = NULL then there is this check: if (result == GNOME_VFS_ERROR_NOT_SUPPORTED || (result == GNOME_VFS_OK && (pfctx->target->type != GNOME_VFS_FILE_TYPE_DIRECTORY))) { result = GNOME_VFS_ERROR_NOT_A_DIRECTORY; } pfctx->target is NULL. dereference. boom."
First of all HEAD does have the http-neon-method.c. Hmm pfctx->target shouldn't be NULL if result is GNOME_VFS_OK. So the crash might be there but the problem itself is likely to be in propfind_result ().
Ok I added some checks so the crash above won't occur anymore. By the way I totally doubt that the stack trace belongs to this bug though! I am about the reslove some URL escaping mixtures at the moment. I am not resassigning the bug though because I dont wanna play ping pong here. I will just close this as FIXED.