sgbotsford

[Log in to get rid of this advertisement]

I have a hacked version of FM 5.5.6 Beta that has run on various redhat distributions since RH6.0

Two weeks ago I upgraded from Fedora Core 4 to Fedora Core 5, and FM now seg faults while setting up memory areas. I will append the last bunch of lines from running struss.

My suspicion is that this is either a change in the way the kernel handles memory mapping or that a library has changed.

1. Anyone know of a change in FC that could cause this.

2. Ideas about how to fix this. This is sufficiently critical, that I will reinstall another distribution if necessary.


open("/usr/lib/libXdmcp.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220\177"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=20312, ...}) = 0
mmap2(0x917000, 21780, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0
x917000
mmap2(0x91c000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE,
3, 0x4) = 0x91c000
close(3) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40
018000
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40
019000
set_thread_area({entry_number:-1 -> 6, base_addr:0x40018d90, limit:1048575, seg_
32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, usea
ble:1}) = 0
mprotect(0x72a000, 4096, PROT_READ) = 0
mprotect(0x6f8000, 12288, PROT_READ) = 0
mprotect(0x724000, 4096, PROT_READ) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---

sgbotsford

Problem solved. Upgraded machine to Fedora Core 6, and FM starts up just fine.



[quote=sgbotsford]I have a hacked version of FM 5.5.6 Beta that has run on various redhat distributions since RH6.0

Two weeks ago I upgraded from Fedora Core 4 to Fedora Core 5, and FM now seg faults while setting up memory areas. I will append the last bunch of lines from running struss.

My suspicion is that this is either a change in the way the kernel handles memory mapping or that a library has changed.

1. Anyone know of a change in FC that could cause this.

2. Ideas about how to fix this. This is sufficiently critical, that I will reinstall another distribution if necessary.