| View previous topic :: View next topic |
| Author |
Message |
boroshan
l33t
Joined: 16 Apr 2003
Posts: 730
Location: upside down
|
 Posted: Mon Aug 25, 2003 5:23 pm Post subject: vi started throwing a segmentation fault |
 |
|
Anyone else still use old style vi? It's just started segfaulting on me for no apparent reason.
It's not all the time, but consistent with certain files upon opening them. I've tried re-emerging but no joy. I suspect its a library issue, possibly related to my running 2.6.0-test4 and/or the latest (masked) nvidia drivers.
vim, incidentally, works just fine, only I prefer vanilla vi myself.
If its not just me I'll submit a bug report. If it is just me I'll try fiddling a bit more first.
_________________
Don't let THEM immanentize the Eschaton! |
|
| Back to top |
|
 |
mslay
n00b
Joined: 19 May 2003
Posts: 40
Location: France
|
| Posted: Mon Aug 25, 2003 5:25 pm Post subject: |
|
|
what did it says ptrace?
_________________
Silent scream, from an unfit Earth... |
|
| Back to top |
|
|
boroshan
l33t
Joined: 16 Apr 2003
Posts: 730
Location: upside down
|
| Posted: Mon Aug 25, 2003 5:45 pm Post subject: |
|
|
I don't seem to have ptrace as a command line util. I found a few kernel headers and a system call, but no command and no ebuild.
what do I need to emerge?
_________________
Don't let THEM immanentize the Eschaton! |
|
| Back to top |
|
|
mslay
n00b
Joined: 19 May 2003
Posts: 40
Location: France
|
| Posted: Mon Aug 25, 2003 6:42 pm Post subject: |
|
|
emerge ptrace
_________________
Silent scream, from an unfit Earth... |
|
| Back to top |
|
|
mslay
n00b
Joined: 19 May 2003
Posts: 40
Location: France
|
| Posted: Mon Aug 25, 2003 6:51 pm Post subject: |
|
|
sorry, I realized now, I was talking about strace not ptrace,I missed some sleep hours last night...
so emerge strace and post the latest lines from strace vi.
_________________
Silent scream, from an unfit Earth... |
|
| Back to top |
|
|
boroshan
l33t
Joined: 16 Apr 2003
Posts: 730
Location: upside down
|
| Posted: Mon Aug 25, 2003 7:23 pm Post subject: |
|
|
okidoki
| Code: | write(1, "\"/etc/make.conf\"", 16) = 16
getpid() = 1405
unlink("/var/tmp/Ex0000001405") = 0
close(3) = 0
stat64("/var/tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=1464, ...}) = 0
concat("/var/tmp/Ex0000001405", O_RDWR|O_CREAT|O_TRUNC|O_EXCL, 0600) = 3
concat("/etc/make.conf", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=13200, ...}) = 0
read(4, "# Co", 4) = 4
lseek(4, 0, SEEK_SET) = 0
access("/etc/make.conf", W_OK) = 0
fstat64(4, {st_mode=S_IFREG|0644, st_size=13200, ...}) = 0
read(4, "# Copyright 2000-2003 Daniel Rob"..., 131072) = 13200
read(4, "", 131072) = 0
fsync(4) = 0
close(4) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
|
_________________
Don't let THEM immanentize the Eschaton! |
|
| Back to top |
|
|
boroshan
l33t
Joined: 16 Apr 2003
Posts: 730
Location: upside down
|
| Posted: Mon Aug 25, 2003 7:28 pm Post subject: |
|
|
and for whatever it may be worth, I did a stack trace from gdb as well:
| Code: | (gdb) where
#0 0x4009de3b in strlen () from /lib/libc.so.6
#1 0x080528fa in getchar ()
#2 0x08053371 in getchar ()
#3 0x0806821a in getline ()
#4 0x0804d1d5 in error ()
#5 0x0804e661 in error ()
#6 0x08069b20 in getline ()
#7 0x080522ef in getchar ()
#8 0x08053bc2 in putchar ()
#9 0x0806b33a in vprintf ()
#10 0x0806b2f8 in printf ()
#11 0x0805148e in getchar ()
#12 0x08050e6d in getchar ()
#13 0x0804b4fa in strcpy ()
#14 0x08060f22 in getline ()
#15 0x0805d84e in getline ()
#16 0x0804bfc6 in strcpy ()
#17 0x08049985 in strcpy ()
#18 0x4003b7a7 in __libc_start_main () from /lib/libc.so.6
|
which suggests its bombing out trying to print an error message to my mind
_________________
Don't let THEM immanentize the Eschaton! |
|
| Back to top |
|
|
mslay
n00b
Joined: 19 May 2003
Posts: 40
Location: France
|
| Posted: Mon Aug 25, 2003 7:30 pm Post subject: |
|
|
have you changed the flags and recompiled glibc?I mean x86 to ~x86 or so?
_________________
Silent scream, from an unfit Earth... |
|
| Back to top |
|
|
boroshan
l33t
Joined: 16 Apr 2003
Posts: 730
Location: upside down
|
| Posted: Mon Aug 25, 2003 10:05 pm Post subject: |
|
|
As far as I'm aware there are only two packages on my system that are compiled with ~x86.
One of them is wine. I'd revert that back to stables, only I wants the sable version of the vidia drivers and 2.6.0 needs them. Of course, I could always revert to the current gaming-sources package again and the whole thing'd probably clear up.
Beyond that... I did recently recompile glibc. I was trasnferring the main drive from a PII machine to an Athlon XP. I did a emerge -e world but I'm not at all sure I didn't mess something up. But that was three weeks ago now and the problem is only two days old. So unless its something weird in the contents (I've been assuming its file size) then I'd have ecpected to stumble across this before then - I use vi a lot. In any event, I'm not so daft as to rebuild world using unstable versions....
I think I might well go back to using 2.4.20 anyway and see if that helps. The 2.6.0 test kernel is ice but still a little choppy compared to gaming sources
_________________
Don't let THEM immanentize the Eschaton! |
|
| Back to top |
|
|
boroshan
l33t
Joined: 16 Apr 2003
Posts: 730
Location: upside down
|
| Posted: Tue Aug 26, 2003 12:27 pm Post subject: sorted! Well, sort of... |
|
|
I booted back into the current gaming-sources kernel, emeged the stable nvidia driver and glx library and guess what? It works again
So, there seems litle doubt that it was related to either the kernel or the nvidia driver. If anyone'd find the data useful I could try booting the new kernel with the nv drivers for xfree86 and see if that causes it, but personally, I'm going to stick with the gaming sources setup for the time being, so the problem evaporates.
mslay - thanks for your help.
_________________
Don't let THEM immanentize the Eschaton! |
|
| Back to top |
|
|
|
Other Things Gentoo
