Jump to content

  • Log In with Google      Sign In   
  • Create Account


#Actualslicer4ever

Posted 14 January 2013 - 06:59 AM

in my experience, a seg-fault cropping up/disappearing with a clean is resonate of a much deeper problem in the code base.

 

This is not to say it very well might be an issue with a bad build, but in general, i've almost always discovered their to be an actual flaw in my code somewhere after heavy analyzing(something that only cropped up because the compiler didn't null all my pointers(and i forgot to explicity set a pointer to null) for me for some reason, or was allowing buffer-overflow's that didn't cause immidiate crash's)

 

edit after L. Spiro's/Karsten_'s posts, i'd like to point out that i only use a single machine for compilation, and i use VS 2010, which auto-detects header changes, and appropriately re-compiles the obj's that include the headers, which is probably why i more often experience such things in form of actual bugs, than bad build's.


#3slicer4ever

Posted 14 January 2013 - 04:33 AM

in my experience, a seg-fault cropping up/disappearing with a clean is resonate of a much deeper problem in the code base.

 

This is not to say it very well might be an issue with a bad build, but in general, i've almost always discovered their to be an actual flaw in my code somewhere after heavy analyzing(something that only cropped up because the compiler didn't null all my pointers(and i forgot to explicity set a pointer to null) for me for some reason, or was allowing buffer-overflow's that didn't cause immidiate crash's)


#2slicer4ever

Posted 14 January 2013 - 04:32 AM

in my experience, a seg-fault cropping up/disappearing with a clean is resonate of a much deeper problem in the code base.

 

This is not to say it very well might be an issue with a bad build, but in general, i've almost always discovered their to be an actual flaw in my code somewhere after heavy analyzing(something that only cropped up because the compiler didn't null all my pointers for me for some reason, or was allowing buffer-overflow's that didn't cause immidiate crash's)


#1slicer4ever

Posted 14 January 2013 - 04:30 AM

in my experience, a seg-fault cropping up/disappearing with a clean is resonate of a much deeper problem in the code base.


PARTNERS