memory fault?
Hi guys,
I'm trying to complete an assignment. The school provides us with sample input files and also shows us what the output will look like. I have tested these continuously, however, when i went to submit it, the school has an auto-testing thing and my codes dont work saying instead I have a memory fault. Any notes on how to fix that?
Thanks
The answer to your question is 101010. Have a nice day!
My best code is written with the delete key.
Oh... that should so be an automated answer...Originally Posted by Prelude
The answer to your question is 101010. Have a nice day!
Sent from my iPadŽ
You're quick, but I'm godly. I made it more geeky.
My best code is written with the delete key.
huh?
>huh?
Exactly! What gave you the idea that anyone would be able to help you with such a vague question?
My best code is written with the delete key.
well i'm really really new to programming and I don't know how else to ask?
Sent from my iPadŽ
>well i'm really really new to programming and I don't know how else to ask?
Common sense transcends skillsets. When asking a question about anything you provide as much information as possible, right? I can tell you things that would cause a memory fault, but if one of them turned out to be your problem, it would be nothing more than dumb luck on my part because you haven't show us any code, and all I would be going on is the phrase "memory fault".
My best code is written with the delete key.
memory fault generally means that you missused pointer somehow. It can mean that you made your strings one size to small (remmember to make room for the null character). It can also mean that you're derefferencing a null pointer. There are other things too.
BTW, I think this is a perfectly valid question. However, lyn_f, you might consider posting your code so we can help you identify the portion of your code that is causing the memmory fault (assuming the program is not too long).
It is too clear and so it is hard to see.
A dunce once searched for fire with a lighted lantern.
Had he known what fire was,
He could have cooked his rice much sooner.
>BTW, I think this is a perfectly valid question.
It would be if we had the context required to answer it. A memory fault is by far the most elusive and frustrating of bugs. They take forever to find because there are so many ways to cause them and their locality is usually ridiculous.
My best code is written with the delete key.
In case you still haven't figured it out, finding the problem takes source code.
So post some.
And don't forget to use [code][/code] tags.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
I disagree. Memory corruptions that do not cause faults are even more elusive, and usually take longer to notice.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
>Memory corruptions that do not cause faults are even more elusive, and usually take longer to notice.
That would be a memory fault as well. Perhaps I should have made it clear that I was talking about a class of bugs rather than a specific system error.
My best code is written with the delete key.
Yes, but lyn_f doesn't know that. He's just asking what a memory fault is, and what are likely causes.
It is too clear and so it is hard to see.
A dunce once searched for fire with a lighted lantern.
Had he known what fire was,
He could have cooked his rice much sooner.
