Segfaults (usually) will produce a core dump if you're compiled with debugging (you probably did) and your system allows it. Following Nick's guide you can then use gdb to examine the core dump against your game's executable file and figure out what broke and where.
There is something called a Segmatation fault in my nohup.out file what is that? more nohup.out Segmentation fault Segmentation fault [snip]
In an Unix-like environment, a process that accesses an invalid memory address receives the SIGSEGV signal. If you're dealing with windows, a process that accesses invalid memory receives the STATUS_ACCESS_VIOLATION exception.
To answer your would-be question segmentation is an approach to memory protection in operating systems. Even though now paging has supersede it for most purposes much of the terminology has remained the same. Ergo "segmentation fault" is a fault(error) in your memory protection scheme. This will occur, as indicated above, when memory is accessed that does not belong to the program in question. (Or is just invalid.) This, frankly, is a much better alternative to crashing/corrupting another legitimate program because of a rogue pointer.
Like I said, you are confusing the lack of symptoms with the lack of underlying problems. A clean compile hardly means that there are no problems; I can write innumerable programs that compile cleanly yet crash. Still, if this works for you, then so be it; just don't think that you've solved the underlying problem. It might come back to bite you later on, and it will be all the harder to debug as you will have masked the symptoms you knew about.
To quote David Haley from the cedit post and the check, I think I know what your talking about there since I cant find the error in my ROM and I really don't understand the gdb thing in all honesty, to it reads like an dead old roman language. my game doesn't have much of a coder just someone who comes in and looks over everything and adds something then goes. Anyways what it does is resets mudschool 6 times then crashes the mud
BTW, just in case you want more than the typical gdb, you might want to check out cgdb Coming from a Windows background, for me it's got much more of an IDE feel. The source window functions very similar to Vim. Anyway, I thought it was nifty.