On 11/05/2010 15:59, Lucas Nussbaum wrote:
Upgrading libpcre3 from version 7.8-3 (in testing) to version 8.02-1 (in
unstable) causes approx 3.3.0 (in stable) to start segfaulting at startup (on
amd64).
It works OK on i386. The version in unstable works on both.
Although I can reproduce this easily, I'm not sure how to go about
tracking down the problem. There are no debugging symbols in the
released binary so gdb doesn't reveal much. When I built approx 3.3.0
from source, it worked (or at least didn't crash on startup, I didn't
try to install it).
pcre_config(0, 0x7fffffffd014, 57, 0x7f7e6fb36900, 0x7fffffffcf40) = 0
pcre_config(1, 0x7fffffffd014, -84616, 0x7f7e6fb36900, 0x7fffffffcf40) = 0
pcre_config(2, 0x7fffffffd014, -84632, 0x7f7e6fb36900, 0x7fffffffcf40) = 0
pcre_config(4, 0x7fffffffd014, -84584, 0x7f7e6fb36900, 0x7fffffffcf40) = 0
Which returned OK, so it didn't crash in these functions. I'm not sure
what ltrace outputs if a signal is received during a library call, does
it output anything for the library call at all? i.e. could there be
another pcre function called after these ones, which ltrace hasn't
output anything for because of the seg fault?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
