[Xastir-Dev] "Caught seg fault"
Chris Bell
cbell at junknet.com
Sun Jan 5 16:11:02 EST 2003
>
> FWIW, the -t option did not generate a core file for me to work against.
>
The debug levels (like '-v 16') did not show which map it was chewing on?
Your shell might be limiting the core dump.
csh/tcsh uses `limit` :
csh% limit core to check it
coredumpsize unlimited
csh% limit core unlimited to set it to allow cores
sh/ksh/bash use `ulimit`:
bash% ulimit -c to check it
unlimited
bash% ulimit -c unlimited to set it to allow cores
`limit` with no args and `ulimit -a` show all the limits.
When it says "Segmentation fault" it should say "core dumped" as
well. If it does, you have to find out where it put it... :)
Hope that helps.
Chris.
More information about the Xastir-dev
mailing list