On Mon, Oct 23, 2006 at 11:52:32PM -0500, Aaron Griffin wrote:

I attempted 2 rather random changes to see if it affects anything - right now I have no way to test this (no 64bit machines), so can you please let me know if it fixes anything? I prefixed the string with the max length, as a safeguard, and switch the unsigned chars to unsigned ints, in the off-chance that _that_ has some effect, though I expect it's string related.

Please let me know either way.

still segfaults. i would suggest asking a shell access from an Arch64 dev, i neither have such a machine phisically. anyway here is the commandline to reproduce the issue: vmiklos@helicon:~/darcs/pacman/src/pacman$ sudo rm -f /var/cache/pacman/pkg/vim* /tmp/pacman.lck; sudo ./pacman -Sw vim --noconfirm resolving dependencies... done. Targets: vim-7.0-2 Total Package Size: 5.0 MB Total Uncompressed Package Size: 16.3 MB Beginning download... :: Retrieving packages from frugalware-current... Internal pacman error: Segmentation fault00:00:00 [ ] 0% Please submit a full bug report, with the given package if appropriate. udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

On 10/25/06, Christian Hamar alias krix wrote:

So the problem still exists. I catched up some backtrace with the not debug binary pacman and seems that it segfaults at FtpRead() function.

That is strange too.

A notice for this, the main progressbar moves to some ~5 or 10% and crashing after that. So it will be some magic buffer overrun somewhere :S

Apparently this does not crash under Arch64, according to Varun: ./pacman -S aterm resolving dependencies... done. looking for inter-conflicts... done. Targets: aterm-1.0.0-2 Total Package Size: 0.1 MB Proceed with upgrade? [Y/n] y :: Retrieving packages from current... aterm-1.0.0-2 73K 13.5K/s 00:00:05 [#######################] 100% checking package integrity... done. checking for file conflicts (1/1) [#######################] 100% (1/1) installing aterm [#######################] 100% So, no segfault for me. :)

On 10/25/06, VMiklos wrote:

On Wed, Oct 25, 2006 at 08:14:31AM -0500, Aaron Griffin wrote:

...

So, no segfault for me. :)

is it a debug-disabled+stripped pacman?

Oh crap, no - let me have him disable debug.