Thread: New Student Error Messages

  1. #1
    Registered User
    Join Date
    Feb 2006

    New Student Error Messages

    I am a new CIS student currently taking a course in Programming I C++.

    I find this to be extremely challenging but also fun. I'm in need of some help. Can someone please explain to me what

    Fatal Error means? This is usually my only error that I encounter

    Thank You

  2. #2
    pwns nooblars
    Join Date
    Oct 2005
    Portland, Or
    If you are serious, that means it is an error that was too severe for your program to recover from.

    If you aren't serious, go away troll.

  3. #3
    Registered User
    Join Date
    Feb 2006
    Thanks. I have been asking this question in class 4 awhile. Received no answer.

    BTW-- I'm not a troll

  4. #4
    Mad OnionKnight's Avatar
    Join Date
    Jan 2005
    Umeň, Sweden
    Fatal means that something will die from it so that means the program got an error which forced it to shut down. :eng101:

  5. #5
    and the hat of int overfl Salem's Avatar
    Join Date
    Aug 2001
    The edge of the known universe
    You could always just post your code which generates a fatal error rather than just saying "I got an error", which is about as useful as a blank message.

  6. #6
    Hardware Engineer
    Join Date
    Sep 2001
    Are you getting these errors when you compile, or when you run your program?

    I suspect they are compile errors. In that case, the compiler should report the line-number where the problem is... or near where the problem is... Often, the compiler doesn't know exactly where the problem is because it doesn't know what you were trying to do. The compiler can get confused... I've had the compiler report hundreds of errors because of one missing curly-brace!

    So, the trick is to compile and test-run a few lines at a time. Start-out all of your programs as "Hello World" type programs, and add one or two lines, test-compile, test-run, add one or two more lines, etc. That way, you will always know where the problems are, and you will only have one or two problems/errors at a time.

    But, don't think you can always write you code in line-number sequence... You can't call a function that doesn't exist yet, etc. But, you can write an empty function, and put-in little temporary cout statements like cout << "I'm in function1() now"; or cout << "X= " << X; so that you can see what your program is doing, and make sure it's working before it's completely done. As you get more experience, you will learn more ways of testing your partially completed code.

    Compile-time errors are the easiest to find, because the compiler trys to tell you what it thinks is wrong.

    Link errors are a little trickier, because you don't get line numbers. But, you usually get a variable name or a function name.

    Run-time bugs are the toughest, because it's up to you to find the problem. Sometimes you can "comment-out" some lines to see if the problem goes-away, or add some of those extra cout statements to try and figure-out what's going-on. And, you can learn to use your compiler's debugger...
    Last edited by DougDbug; 02-22-2006 at 07:56 PM.

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Updating in a sequential file?
    By Ronnyv1 in forum C Programming
    Replies: 1
    Last Post: 03-24-2009, 04:41 PM
  2. Database assignment is Killing me!
    By Boltrig in forum C Programming
    Replies: 2
    Last Post: 11-29-2007, 03:56 AM
  3. LinkList Sorting in C
    By simly01 in forum C Programming
    Replies: 3
    Last Post: 11-25-2002, 01:21 PM
  4. Creating a student grade book-how?
    By Hopelessly confused in forum C Programming
    Replies: 5
    Last Post: 10-03-2002, 08:43 PM
  5. A few tips please...
    By gems in forum C++ Programming
    Replies: 4
    Last Post: 04-11-2002, 02:28 PM