Re: unkwon exception throwing
On May 3, 3:29 pm, Juha Nieminen <nos...@thanks.invalid> wrote:
Philipp Kraus <philipp.kr...@flashpixx.de> wrote:
Compiler is g++ under OSX 10.5 & 10.6
Compile the program with the -g compiler option and then run the
program with gdb (iow. "gdb ./yourprogram" and then "run"), and if/when
it crashes it should show the line where it does. (If the line is
nondescriptive eg. because it's in some system library, write "bt"
to get a backtrace. The first line in the backtrace which is in your
own code is usually a good indicative.)
Except when it's not:-). Corrupting the free space arena is a
frequent cause of such problems, and of course, the "crash"
occurs in an allocation totally unrelated to where the error
was.
(Such problems are really fun to debug:-). To top it off, the
last time I had to attack one, 1) I'd just entered a new
company, and had never seen the half a million lines of code
before I was asked to debug it, and 2) the actual problem was
due to the compiler generating wrong code in a tight loop. Both
very exceptional cases, which multiply the difficulty by several
orders of magnitude. On the other hand, without such difficult
problems, I'd be hard pressed to justify how much I'm paid, so I
won't complain too much.)
--
James Kanze