CVS Crash when using -r

Bug #76249 reported by Chmouel Boudjnah
2
Affects Status Importance Assigned to Milestone
cvs (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: cvs

We have experienced crashes with cvs binary from edgy, and i am not sure if it's a specific ubuntu problem a config problem or a cvs (upstream problem).

When using cvs with -r we are getting this segfault :

-$ cvs up -dP -r mysource_3-12-0-branch .
cvs update: Updating .
? foo
cvs update: Updating cache
cvs update: Updating core
[...]
*** glibc detected *** cvs: double free or corruption (fasttop): 0x080ef818 ***
======= Backtrace: =========
/lib/libc.so.6[0xb7e37082]
/lib/libc.so.6(__libc_free+0x84)[0xb7e38704]
cvs[0x8078110]
cvs[0x80a5bf2]
cvs[0x8078b3a]
/lib/libc.so.6(__libc_start_main+0xdc)[0xb7de98cc]
cvs[0x804b8d1]
======= Memory map: ========
08048000-080ea000 r-xp 00000000 fe:00 1623466 /usr/bin/cvs
080ea000-080eb000 rw-p 000a2000 fe:00 1623466 /usr/bin/cvs
080eb000-0816f000 rw-p 080eb000 00:00 0 [heap]
b7c00000-b7c21000 rw-p b7c00000 00:00 0
b7c21000-b7d00000 ---p b7c21000 00:00 0
b7d65000-b7d6f000 r-xp 00000000 fe:00 3211355 /lib/libgcc_s.so.1
b7d6f000-b7d70000 rw-p 00009000 fe:00 3211355 /lib/libgcc_s.so.1
b7d7d000-b7d7e000 rw-p 00000000 fe:01 9928739 /home/cvs/fudge/wysiwyg/plugins/visual_aid/images/th.png,v
b7d7e000-b7d7f000 rw-p b7d7e000 00:00 0
b7d86000-b7dbb000 r--s 00000000 fe:00 3342434 /var/db/nscd/passwd
b7dbb000-b7dbd000 rw-p b7dbb000 00:00 0
b7dbd000-b7dbf000 r-xp 00000000 fe:00 3211302 /lib/libdl-2.4.so
b7dbf000-b7dc1000 rw-p 00001000 fe:00 3211302 /lib/libdl-2.4.so
b7dc1000-b7dd0000 r-xp 00000000 fe:00 3211327 /lib/libpthread-2.4.so
b7dd0000-b7dd2000 rw-p 0000e000 fe:00 3211327 /lib/libpthread-2.4.so
b7dd2000-b7dd4000 rw-p b7dd2000 00:00 0
b7dd4000-b7eed000 r-xp 00000000 fe:00 3211299 /lib/libc-2.4.so
b7eed000-b7eef000 r--p 00118000 fe:00 3211299 /lib/libc-2.4.so
b7eef000-b7ef1000 rw-p 0011a000 fe:00 3211299 /lib/libc-2.4.so
b7ef1000-b7ef4000 rw-p b7ef1000 00:00 0
b7ef4000-b7efb000 r-xp 00000000 fe:00 3211356 /lib/libpam.so.0.79
b7efb000-b7efc000 rw-p 00006000 fe:00 3211356 /lib/libpam.so.0.79
b7efc000-b7f0f000 r-xp 00000000 fe:00 1624162 /usr/lib/libz.so.1.2.3
b7f0f000-b7f10000 rw-p 00012000 fe:00 1624162 /usr/lib/libz.so.1.2.3
b7f10000-b7f11000 rw-p b7f10000 00:00 0
b7f11000-b7f22000 r-xp 00000000 fe:00 3211305 /lib/libnsl-2.4.so
b7f22000-b7f24000 rw-p 00010000 fe:00 3211305 /lib/libnsl-2.4.so
b7f24000-b7f26000 rw-p b7f24000 00:00 0
b7f26000-b7f2b000 r-xp 00000000 fe:00 3211301 /lib/libcrypt-2.4.so
b7f2b000-b7f2d000 rw-p 00004000 fe:00 3211301 /lib/libcrypt-2.4.so
b7f2d000-b7f54000 rw-p b7f2d000 00:00 0
b7f54000-b7f5a000 r-xp 00000000 fe:00 3211366 /lib/librt-2.4.so
b7f5a000-b7f5c000 rw-p 00005000 fe:00 3211366 /lib/librt-2.4.so
b7f69000-b7f6b000 rw-p b7f69000 00:00 0
b7f6b000-b7f84000 r-xp 00000000 fe:00 3211296 /lib/ld-2.4.so
b7f84000-b7f86000 rw-p 00018000 fe:00 3211296 /lib/ld-2.4.so
bfb91000-bfba6000 rw-p bfb91000 00:00 0 [stack]
ffffe000-fffff000 ---p 00000000 00:00 0 [vdso]
cvs [update aborted]: received abort signal

i can reproduce the problem with stock cvs and cvs version of cvs.

We are using ldap login and if i stop nscd i get simply a freeze of cvs hang and doing nothing.

I could not reproduce that when we were using dapper.

Let me know if you need more info, would be great if you can guide me on a path where to look at.

Cheers, Chmouel.

Revision history for this message
Chmouel Boudjnah (chmouel) wrote :

FYI, in case of somebody ask this could not be a memory problem i had DELL who come here and changed the memory banks.

Revision history for this message
Chmouel Boudjnah (chmouel) wrote :

And FYI again there is no such problem using cvs-1.12.9 from debian sarge on edgy.

Revision history for this message
Sebastian Rode (sebastian-ro-deactivatedaccount) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update to version 1:1.12.13-5build1 witch is in feisty. Edgy isn't supported any more. Feel free to submit any future bugs you may find.

Changed in cvs:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.