[AD] Documentation is wrong about ulimit parameter |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Hi.
The help documentation says incorrectly that ulimit -c 0 will allow
cores to be dumped. -c 0 makes cores not dump under my system, hence the
proposed fix. I'm not commiting this because maybe ulimit has different
behaviours under different unices, more precisely, I remember Eric saying
that ulimit -c 0 worked for Suse. Could you please verify which setting
are you using with ulimit?
Index: help._tx
===================================================================
RCS file: /cvsroot/alleg/allegro/docs/src/help._tx,v
retrieving revision 1.5
diff -u -r1.5 help._tx
--- help._tx 22 Sep 2002 15:32:11 -0000 1.5
+++ help._tx 1 Oct 2002 20:52:05 -0000
@@ -154,7 +154,8 @@
Look at your filesystem: there should be a file named core or something
similar with information telling you exactly where the crash occurred.
If there is no core, check your environment settings, under bash this is
- done with the 'ulimit -a' command. Usually 'ulimit -c 0' will do fine.
+ done with the 'ulimit -a' command. Usually 'ulimit -c unlimited'
+ somewhere in your login scripts sould work fine.
Just like with djgpp, to make sense of the core, you should compile your
program with debugging information (using the -g switch), and then run