[cvsnt-dev] Re: 2.5.02.2040 problems

David Somers dsomers at omz13.com
Sat Jul 30 13:02:10 BST 2005


Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


Tony Hoyle wrote:

> David Somers wrote:
> 
>> The segfault is happening in cvs::str_prescan() from /usr/lib/libcvsapi.
>> 
>> Is there any easy way that I can build cvsnt with debugging symbols? Then
>> I should be able to back trace to see where this is coming from. (I guess
>> its being passed some bogus data).
>> 
> It should give enough information anyway..  Just adding -g to CFLAGS
> will add the source information.
> 
> The only thing str_prescan does is check for null arguments.  It never
> does anything else with the data it's passed.

Program received signal SIGSEGV, Segmentation fault.
0xb7fa259b in str_prescan (fmt=0xb7fc859b "u", va=0xbfffec1c "a\t") at
cvs_string.cpp:203
        in cvs_string.cpp

The backtrace leads to line 140
zc.BrowseForService(SERVICE,CZeroconf::zcAddress)
in src/info.c

So it looks like something in cvsapi/Zeroconf.cpp is going weird... 

Tracing shows

[snip]
13:57:55:   -> wrap_add(*.xls -kb, 0, 0)
13:57:55:   -> wrap_add(*.zip -kb, 0, 0)
13:57:55:   -> wrap_add(*.Z -kb, 0, 0)
13:57:55:   -> Zeroconf ipv4 response from caxton.local: 192.168.42.254
Segmentation fault

So after it gets the first response something goes wrong.

-- 
David Somers
VoIP: FWD 622885
PGP Key = 7E613D4E
Fingerprint = 53A0 D84B 7F90 F227 2EAB  4FD7 6278 E2A8 7E61 3D4E


More information about the cvsnt-dev mailing list