That sounds familiar... are there bitfields next to a memory allocation
zone boundary? GCC will issue read instructions that read off the
bitfield (documented in the manual --- can't really complain), so you
can get a segfault reading a bitfield if GCC emits instructions at
compile time that read off the allocation edge at run time...
On 1/2/11 10:09 , Eliot Miranda wrote:
Hi All,
looks like there are issues running Cog on 64-bit linux. I only
have a 32-bit one to hand so it'll be a while before I can look at this.
BTW, it would really help if when people post bugs they give
- a URL to the image and changes, not just a name like Pharo 1.1.1. A
pointer to the exact bits eliminates any possibility that I will fetch
the wrong image and not be able to reproduce
- the exact directory something is installed in, not just the name but
the full path, and whether it is remote ounted or not. I just fixed a
crash on windows for Torsten that didn't show on a remote-mounted drive
but caused a hard crash if installed as c:\pharo. So saying "its in
coglinux/" isn;t being precise enough.
TIA
best
Eliot
On Sun, Jan 2, 2011 at 11:01 AM, Philippe Marschall <[email protected]
<mailto:[email protected]>> wrote:
On 02.01.2011 16:50, Eliot Miranda wrote:
> Hi Philippe,
>
> what image, what OS and what directories are the vm and image
> installed in (yes it can make a difference).
- Pharo 1.1.1
- $uname -a
Linux 2.6.36-gentoo-r4 #1 SMP PREEMPT Sun Dec 12 19:02:46 CET 2010
x86_64 Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz GenuineIntel GNU/Linux
- image lies in some subdirectory of the user home, Cog is extracted in
the same folder, so it's under coglinux/
Cheers
Philippe
