* Lars Gullik Bjønnes <[EMAIL PROTECTED]> [010307 14:59]:
> Baruch Even <[EMAIL PROTECTED]> writes:
>
> | Hello,
> |
> | I believe we should add a printing to the Assert definition so that it
> | will be obvious when a core dump is caused by some assert, it would be
> | great if it included the line and file of the assert, and it would be
> | best if it printed the assert condition itself, but I do not know how to
> | achieve that in C++.
> |
> | Should I provide a patch for this?
>
> then you have to use a macro.
I dont mind even placing in Assert() a line that does:
lyxerr << "ASSERT Failed!\n";
This will suffice.
> why can't you use the debugger?
It's not a question of using the debugger, this is just to make bug
reports (like John's latest bug finding in IG) more sensible.
Learning that it was a core dump doesn't help me to understand it.
Knowing it's an assert that failed will give me more clues to decipher
the reason.
In this case the problem was trivial enough to find, in other cases it
might not be so trivial.
--
Baruch Even
http://baruch.ev-en.org/
