Hoi!
Thorsten Haude wrote:
* Daniel Baulig wrote (2006-05-23 20:10):
Thorsten Haude wrote:
* Daniel Baulig wrote (2006-05-23 17:53):
When I have nedit open and the search dialog up pressing ctrl+v crashes
nedit.
Is there a core? What is the result of 'nedit -V'?
What is "a core"?
It's a file (aptly called 'core', sometimes 'core.$PID') created by
the OS if a process crashes. The file contains information about the
process the moment it crashed and can help in debugging. This is also
called 'throwing a core' or 'core dump'.
The file is not always created for various reasons. If it is not,
please send the result of 'ulimit -a'.
I suppose the file should be created in the user's home directory, which
it is not.
That's the ouput of ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
max nice (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) unlimited
max rt priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
However, I just figured, that the term "crash" might not be 100%
correct. Actually nedit does not crash totally, but sort of hang. I
cannot press any control elements, and it will not redraw any elements
anymore. However, I have to kill it to get rid of it completely.
Greets
Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
