Opened 13 years ago

Closed 13 years ago

Last modified 11 years ago

#1456 closed bug (duplicate)

linux tools cause glibc detected double free or corruption on x86-64

Reported by: engima Owned by: bonefish
Priority: normal Milestone: R1
Component: Build System Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Platform: x86-64


I have attempted to build a fresh checkout of the tree on a Core2 system under Gentoo Linux using a 64 bit environment. Building items for use under Haiku appears to work successfully (at least no errors are generated), however tools built for use under the Linux host (eg xres or rc) generate glibc faults on every execution. Example output is attached.

When running the faulting commands through valgrind there are a number of interesting memory related errors detected, of note is an invalid write of size 8. Example output is attached. After further investigation it appears that the size of uint32 is incorrect for the host, it actually turns out to be 64bits.

If additional details are required I can attach as needed, error is easily reproducible on my system.

Attachments (2)

jam-xres (7.8 KB ) - added by engima 13 years ago.
Output of 'jam -q xres'
valgrind-output (8.4 KB ) - added by engima 13 years ago.
Output of valgrind execution of xres

Download all attachments as: .zip

Change History (4)

by engima, 13 years ago

Attachment: jam-xres added

Output of 'jam -q xres'

by engima, 13 years ago

Attachment: valgrind-output added

Output of valgrind execution of xres

comment:1 by bonefish, 13 years ago

Resolution: duplicate
Status: newclosed

We still don't really support building on 64 bit machines (in 64 bit mode). So this is more or less a duplicate of #845.

comment:2 by mmadia, 11 years ago

Platform: x64x86-64
Note: See TracTickets for help on using tickets.