Summary: | [vim7] gvim-7.0_alpha20050721 / xorg-x11-6.8.2-r2: System destabilization when opening a file using a wildcard | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Anthony Gorecki <anthony> |
Component: | Current packages | Assignee: | Vim Maintainers <vim> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2005.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Anthony Gorecki
2005-07-31 23:21:01 UTC
Anthony: We need more information and gdb backtraces if possible. What does 'open a wildcarded file' mean? I was referring to the list of files you'd expect to be generated by Bash upon entering a wildcard as part of a file name: src/Version*.cs In addition to the above, I also attempted to open a nonexistent file using gvim and encountered the same erroneous behavior. On that occasion, I had attempted to open "src/VersionString." As for the backtraces, I'll see if I can capture any of them before the system crashes, but I can't make any guarantees. I tried to capture a backtrace just now and accomplished nothing other than necessitating a reboot. I'll post the test results in subsequent comments since I'm likely to lose my existing remarks. not sure why you CC'd vim@ when that's who it's assigned to... Sorry, it wasn't intentional; Firefox's SessionSaver extension is still buggy. I can't reproduce this one, so I think I'll need a backtrace. Try using X11 forwarding if getting one locally doesn't work. Please retry with 20050809. If it's still a problem, please reopen with a backtrace. This problem has been fixed in the newer version, thanks. |