Re: [Gcl-devel] building gcl-2.6.12: raw_gcl segfaults

[Camm Maguire]

Greetings!  In the failing environment, there is apparently some wrapper
to open() which is interfering with a read of /proc/meminfo:

17104 brk(0x800d12000)                  = 0x800d12000
17104 brk(0x800d16000)                  = 0x800d16000
17104 brk(0x800d18000)                  = 0x800d18000
17104 brk(0xd1b000)                     = 0xd1b000
17104 open("/proc/meminfo", O_RDONLY)   = 3
17104 read(3, "MemTotal:        8074492 kB\nMemF"..., 4096) = 1011
17104 close(3)                          = 0
17104 brk(0xcd9e3000)                   = 0xcd9e3000
17104 stat("/proc/17104/exe", {st_mode=S_IFREG|0755, st_size=4446024, ...}) = 0

vs

16803 brk(0x800d0a000)                  = 0x800d0a000
16803 brk(0x800d12000)                  = 0x800d12000
16803 brk(0x800d16000)                  = 0x800d16000
16803 brk(0x800d18000)                  = 0x800d18000
16803 brk(0xd1b000)                     = 0xd1b000
16803 stat("/proc/meminfo", {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
16803 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x1f} ---
16803 fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 4), ...}) = 0
16803 write(1, "\nUnrecoverable error: ", 22) = 22
16803 write(1, "S", 1)                  = 1
16803 write(1, "egmentation violation.", 22) = 22


This method of determining the runtime available memory has been
replaced in 2.6.13pre with (hopefully) more robust alternatives.  But
hopefully this should point out what is going on.

Please let me know what you find out and we might make an FAQ or
something. 

Take care,
-- 
Camm Maguire                                        address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah