Segmentation fault hell in D

Jonathan M Davis jmdavisProg at gmx.com
Fri Jun 8 11:29:54 PDT 2012


On Friday, June 08, 2012 19:30:57 Jarl André" 
<jarl.andre at gmail.com>@puremagic.com wrote:
> Evry single time I encounter them I yawn. It means using the next
> frickin hour to comment away code, add more log statements and
> try to eleminate whats creating the hell of bugz, segmantation
> fault. Why can't the compiler tell me anything else than the fact
> that i have referenced data that does not exist? Thanks I knew
> that. Now, please tell me where the error occured.... Jeezes.

Turn on core dumps and use gdb. It'll give a backtrace and allow you to look 
at the state of the program when the segfault occured. That's pretty much the 
standard way to figure out what happened when a segfault occurs.

- Jonathan M Davis


More information about the Digitalmars-d-learn mailing list