[fpc-pascal] How to analyze a core dump?

[Luca Olivetti]

En/na Luca Olivetti ha escrit:
> Hello,
> 
> I'm trying to debug a segment violation, I compiled the program with -g, 
> but analyzing the core dump isn't really helpful, maybe the "warning 
> can't read pathname for load map" is the cause? Or it's possible that 
> it's caused by some of the c libraries used having no debug symbols? Any 
> hint?
> Here's my gdb session:
> 
> 
> $ gdb ./botphone core.28682
[...]
> Core was generated by `./botphone -v -v -v -c /home/luca/.linphonerc -C 
> /home/luca/agenda'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x080593ea in SYSTEM_GETERRNO$$LONGINT ()
> (gdb) bt f
> #0  0x080593ea in SYSTEM_GETERRNO$$LONGINT ()
> No symbol table info available.
> #1  0x08060442 in SYSTEM_REENABLE_SIGNAL$LONGINT$$BOOLEAN ()
> No symbol table info available.
> #2  0x08060580 in SYSTEM_SIGNALTORUNERROR$LONGINT$PSIGINFO$PUCONTEXT ()
> No symbol table info available.
> #3  0x08059bec in ?? ()
> No symbol table info available.
> #4  0x0000000b in ?? ()
> No symbol table info available.
> #5  0xb6b5412c in ?? ()
> No symbol table info available.
> #6  0xb6b541ac in ?? ()
> No symbol table info available.
> #7  0x0000000b in ?? ()
> No symbol table info available.
> #8  0x00000000 in ?? ()
> No symbol table info available.
> (gdb)

No suggestions? Is there some special option (apart from -g) that I 
should specify to compile/link my program?

Bye
-- 
Luca