[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: crash on removal (w/ locking)

From: Justin Erenkrantz <jerenkrantz_at_apache.org>
Date: 2003-01-07 20:46:35 CET

--On Tuesday, January 7, 2003 12:15 PM -0600 Ben Collins-Sussman
<sussman@collab.net> wrote:

> jerenkrantz, this is your bug. I've never seen mod_dav_unlock. :-)

Well, I didn't write the auto-versioning code, either. ;-)

>> The relevant portion of the stack trace:
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x403f9c17 in dav_auto_checkin (r=0x8191af0, resource=0xbffff714,
>> undo=0, unlock=1, av_info=0x0) at util.c:2022
>> 2022 if (av_info->parent_resource != NULL &&
>> av_info->parent_resource->working
>> (gdb) bt
>> # 0 0x403f9c17 in dav_auto_checkin (r=0x8191af0,
>> # resource=0xbffff714,
>> undo=0,
>> unlock=1, av_info=0x0) at util.c:2022
>> # 1 0x403fa3ee in dav_unlock_walker (wres=0xbffff704, calltype=1)
>> at util_lock.c:423

We can add a simple non-NULL check against av_info, but I have no
clue if that is the *right* thing to do here. Oh, Greg?? -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 7 20:47:32 2003

This is an archived mail posted to the Subversion Dev mailing list.