exe.stackdump

This is a discussion on exe.stackdump within the C Programming forums, part of the General Programming Boards category; I am writing a new program for class and I am trying to run it after every few strips of ...

  1. #1
    Registered User
    Join Date
    Oct 2007
    Posts
    9

    exe.stackdump

    I am writing a new program for class and I am trying to run it after every few strips of code adding more each time it compiles properly. The first few times it ran fine, then adding new code I got a "segmentation fault (core dumped)" error and it created a .exe.stackdump file

    Can anyone tell me what this means? It has happened before and I kept debugging until I got it fixed but I was just curious to know what this means...maybe it'll help me debug faster if I know what I'm looking for!

  2. #2
    Kernel hacker
    Join Date
    Jul 2007
    Location
    Farncombe, Surrey, England
    Posts
    15,677
    Yes, .exe.stackdump is a "core dump file", which is essentially a copy of the memory from when your application was running [only that applications' memory]. You can use gdb to analyze a core-dump file. Or run the app again inside gdb, and it will show you exactly where you're app is going wrong [that is, if you can easily make that happen - some errors can be hard to find becasue they rely on many different factors being "wrong" at the same time, e.g the right input, running out of memory "at the wrong place", timing between events or what have you - in which case a core-dump of the failure can be a God-send, because you can at least spot where it crashed, and often figure out parts of "how you got there".]

    --
    Mats
    Compilers can produce warnings - make the compiler programmers happy: Use them!
    Please don't PM me for help - and no, I don't do help over instant messengers.

  3. #3
    Registered User
    Join Date
    Oct 2007
    Posts
    9
    thank you

Popular pages Recent additions subscribe to a feed

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21