Hi,
On Sun, Aug 25, 2002 at 12:13:50PM -0500, David W. Chapman Jr. wrote:
This is exactly the problem I'm seeing and would explain why
portupgrade -f fixes the problem for the port that causes the segfault.
Shouldn't pkg_version handle this a little more gracefully?
Can someone with a src
Can someone with a src commit bit please do the honours...
Cool, thanks for the quick fix!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
It seems when pkg_version hits an installed port that has no origin
found it segfaults. I have found other people to verify that it
segfaults for them too. DWhite seems to think that it may be pointer
corruption in libc, specifically snprintf, fopen, strlcpy or strncpy
Here is the backtrace
It seems when pkg_version hits an installed port that has no origin
found it segfaults. I have found other people to verify that it
segfaults for them too. DWhite seems to think that it may be pointer
corruption in libc, specifically snprintf, fopen, strlcpy or strncpy
Have you checked
Have you checked your /var/db/pkg/port_name/+CONTENTS files? For some
reason some ports on my relatively stale -CURRENT box had these files
truncated to zero length, and this caused some package tools (namely
pkg_version) to crash. The procedure to read plist simply returns with
all plist
