Re: [Bug-gnubg] Segmentation fault when clicking on Settings - Appearence

[Jim Segrave]

On Thu 24 Mar 2005 (22:18 +0000), Barbara & Alessio Medici wrote:
> On Monday 21 March 2005 12:44, Jim Segrave wrote:
> > I assume when gnubg dies, it generates a core file in the current
> > directory. Could you do the following:
> 
> Sorry for the delay.
> Gnubg does not create any core file.
> Should I compile with some special flag?

If it dies with a SIGSEGV, then the OS should make a core file. This
is something which can be controlled by the user. On linux try

address@hidden:/home/jes% ulimit -a
core file size        (blocks, -c) unlimited
data seg size         (kbytes, -d) unlimited
file size             (blocks, -f) unlimited
max locked memory     (kbytes, -l) 32
max memory size       (kbytes, -m) unlimited
open files                    (-n) 1024
pipe size          (512 bytes, -p) 8
stack size            (kbytes, -s) 8192
cpu time             (seconds, -t) unlimited
max user processes            (-u) 1023
virtual memory        (kbytes, -v) unlimited

If core file size is set to 0, then you won't get a core file. Then
try ulimit -c unlimited. This may not be allowed (you can't always
raise it as a non-root user). If you find that is a problem, check to
see if there is a limit set in /etc/security/limits.conf and (as root)
change that. Check that there is no ulimit being set in /etc/profile
or in your home directory .profile files.

-- 
Jim Segrave           address@hidden