Bug#422469: gjdoc: upgrade fails with "invalid pointer" when /proc not mounted

Yann Dirson ydirson at altern.org
Sun May 6 09:58:42 UTC 2007


Package: gjdoc
Version: 0.7.8-1
Severity: normal

When uprading my unstable chroot, I got the following failure.  As is
obvious from the trace, /proc is not mounted for some reason, but the
rest of the trace seems to imply that this error condition was not
properly caught.

As expected, mounting /proc allowed the upgrade to proceed.

Preparing to replace gjdoc 0.7.7-6 (using .../gjdoc_0.7.8-1_i386.deb) ...
Unpacking replacement gjdoc ...
GC Warning: Couldn't read /proc/stat
GC Warning: GC_get_nprocs() returned -1
*** glibc detected *** gcj-dbtool-4.1: munmap_chunk(): invalid pointer: 0xb75ecc01 ***
======= Backtrace: =========
/lib/libc.so.6(cfree+0x1bc)[0xb5e6283c]
/lib/libpthread.so.0(pthread_attr_destroy+0x26)[0xb5f7ea96]
/usr/lib/libgcj.so.71[0xb75f26b9]
/usr/lib/libgcj.so.71[0xb75ee10c]
/usr/lib/libgcj.so.71[0xb75ee193]
/usr/lib/libgcj.so.71[0xb75e8862]
/usr/lib/libgcj.so.71(_Z10_Jv_InitGCv+0x5a)[0xb6c054ea]
[0xb7f4a000]
======= Memory map: ========
dpkg: warning - old post-removal script returned error exit status 2
dpkg - trying script from the new package instead ...
GC Warning: Couldn't read /proc/stat
GC Warning: GC_get_nprocs() returned -1
*** glibc detected *** gcj-dbtool-4.1: munmap_chunk(): invalid pointer: 0xb7619c01 ***
======= Backtrace: =========
/lib/libc.so.6(cfree+0x1bc)[0xb5e8f83c]
/lib/libpthread.so.0(pthread_attr_destroy+0x26)[0xb5faba96]
/usr/lib/libgcj.so.71[0xb761f6b9]
/usr/lib/libgcj.so.71[0xb761b10c]
/usr/lib/libgcj.so.71[0xb761b193]
/usr/lib/libgcj.so.71[0xb7615862]
/usr/lib/libgcj.so.71(_Z10_Jv_InitGCv+0x5a)[0xb6c324ea]
[0xb7f77000]
======= Memory map: ========
dpkg: error processing /var/cache/apt/archives/gjdoc_0.7.8-1_i386.deb (--unpack):
 subprocess new post-removal script returned error exit status 2




More information about the pkg-java-maintainers mailing list