[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

aterm segmentation fault

Aterm has suddenly decided to stop working. When I call it from the menu it fails to start. When trying to run a command that uses aterm through nedit I receive a segmentation fault error. Running an strace verifies the segmentation fault, though the results of the strace are pretty much Greek to me. Bash works correctly, though xterm is also affected by this problem. When I attempt to run xterm it ties up all my CPU, and I can't do anything else. I'm forced to reboot. I installed rxvt to check it too, and it produces that same results as xterm.

This all occured after I changed my video card. I was using an old Nvidia TNT2 and installed an Nvidia GeForce FX5200. Aterm worked before this but not after. I have removed and installed aterm to no success. I've tracked down all the common files between aterm, xterm, and rxvt and can't find a bug report that describes my problem, and I can't find anything on google, so I'm at a loss on how to fix this problem. Any ideas?

Ending result of strace:

set_thread_area({entry_number:-1 -> 6, base_addr:0xb73156c0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0
munmap(0xb7f77000, 35648)               = 0
brk(0)                                  = 0x8067000
brk(0x8088000)                          = 0x8088000
open("/dev/zero", O_RDWR)               = 3
mmap2(NULL, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7f7e000
close(3)                                = 0
getpid()                                = 2919
mmap2(NULL, 397312, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb72b4000 modify_ldt(17, {entry_number:666, base_addr:0x8067320, limit:512, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:0, seg_not_present:0, useable:1}, 16) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

Reply to: