kicad-developers team mailing list archive

[Lorenzo Marcantonio <l.marcantonio@xxxxxxxxxxxx>]

Still wrestling with the random fault when doing a module change.
Sometimes it segfaults, sometimes it throws a std:bad_alloc exception.

Usually symptoms of an heap smash...

However it's catched by wx and pops up a dialog:

Unhandled exception class: St9bad_alloc  what: std::bad_alloc

Totally unuseful. At that time the stack is already unwound.

I want it to die on the throw :D segfaults, abort, trap whatever, just
dump the fsck core so that I could see what was happening!

Any idea?

-- 
Lorenzo Marcantonio
Logos Srl