Hi :)
* Good news
If the value for ulimit was set back to 0, than it's not possible
to set it again to another value, but this is possible again,
after the next startup.
* Bad news
[EMAIL PROTECTED]:~> ulimit -c
0
[EMAIL PROTECTED]:~> ulimit -c 1234567890
[EMAIL PROTECTED]:~> ulimit -c
1234567890
[EMAIL PROTECTED]:~> ./broken
Segmentation fault (core dumped)
[EMAIL PROTECTED]:~> gdb broken core
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show
copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux"...
warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib64/libc.so.6...done.
Loaded symbols for /lib64/libc.so.6
Reading symbols from /lib64/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Core was generated by `./broken'.
Program terminated with signal 11, Segmentation fault.
[New process 3674]
#0 0x000000000040045f in main ()
(gdb) where
#0 0x000000000040045f in main ()
Current language: auto; currently asm
(gdb) quit
Suse and 64 Studio create core files for "broken", it looks like
"qsynth" and "jackd" where killed because of an error, but without any
error. It might be impossible to get a core file. On the off chance that
I'll get a core file, did I used gdb correctly?
For a bug report I would copy everything between "(gdb) where" and
"(gdb) quit" and nothing else, right? I don't need to attach the core
file, but I need to keep it, if I get a request to run gdb with other
options, is this correct?
Cheers,
Ralf
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
