Segmentation Fault

[jsgroby]

I have a Segmentation Fault: 11 on my Mac. Testing my engine. I am wanting to use gdb to analyze what happened, but I cannot locate a core file. Do I need to set up something at the system level to instruct the machine to dump a core file during a segfault in OSX?

Is there a way to analyze what is happening without the core file? Like can I run gdb then execute the program and attach to the pid or something like that?

Thanks for your consideration.

Jeff

[jsgroby]

I have a Segmentation Fault: 11 on my Mac. Testing my engine. I am wanting to use gdb to analyze what happened, but I cannot locate a core file. Do I need to set up something at the system level to instruct the machine to dump a core file during a segfault in OSX?

Is there a way to analyze what is happening without the core file? Like can I run gdb then execute the program and attach to the pid or something like that?

Thanks for your consideration.

Jeff

Found it. My ulimit-c was set to 0. I set it to unlimited, ran it again and got the dump in the /cores directory on my system. Now I can run gdb with my engine and the core and see what happened.

[zullil]

I have a Segmentation Fault: 11 on my Mac. Testing my engine. I am wanting to use gdb to analyze what happened, but I cannot locate a core file. Do I need to set up something at the system level to instruct the machine to dump a core file during a segfault in OSX?

Is there a way to analyze what is happening without the core file? Like can I run gdb then execute the program and attach to the pid or something like that?

Thanks for your consideration.

Jeff

Found it. My ulimit-c was set to 0. I set it to unlimited, ran it again and got the dump in the /cores directory on my system. Now I can run gdb with my engine and the core and see what happened.

You might also look at the .crash file. Check /Library/Logs/CrashReporter and ~/Library/Logs/CrashReporter.

[jsgroby]

I have a Segmentation Fault: 11 on my Mac. Testing my engine. I am wanting to use gdb to analyze what happened, but I cannot locate a core file. Do I need to set up something at the system level to instruct the machine to dump a core file during a segfault in OSX?

Is there a way to analyze what is happening without the core file? Like can I run gdb then execute the program and attach to the pid or something like that?

Thanks for your consideration.

Jeff

Found it. My ulimit-c was set to 0. I set it to unlimited, ran it again and got the dump in the /cores directory on my system. Now I can run gdb with my engine and the core and see what happened.

You might also look at the .crash file. Check /Library/Logs/CrashReporter and ~/Library/Logs/CrashReporter.

Thanks, I was able to get part of the backtrace from that crash file which then allowed me to home in on the problem.

Jeff