ah. now I see. it's a little clearer to me now. basicly it's due to bad programming then? and not necissarly on the part of the compiler either. from what kirk just posted, it's either the fault of the coder him/herself or it's simplya memory issue. Shaun.. "We realise we have a problem with communication. However, we're not going to discuss it with our staff." EMAIL: shauno at goanna.net.au ICQ: 76958435 YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on www.jong.com:6667 On 15 Jun 2001, Kirk Reiser wrote: > A segfault or segmentation fault or violation is when a pointer in the > code tries to access memory outside the range allocated as user space > by the operating system. I really mean outside your user memory > space. There are many reasons for getting segfaults but the most > common is when the programmer didn't use a memory pointer correctly in > their code. In a program which doesn't have all of it's components > installed, a segfault will occur because the program which faulted > tried to access memory, such as shared, and it wasn't available. The > o.s. says, woops you're trying to get out of your allowable range, > naughty naughty. > > Kirk > > -- > > Kirk Reiser The Computer Braille Facility > e-mail: kirk at braille.uwo.ca University of Western Ontario > phone: (519) 661-3061 > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup >
