Boost assertions closes the debugger

[zabzonk]

Actually, cancel that. I do get a break in the debugger, but the cursor is not accurately positioned after the assert - it seems like in the previous code it got located there by chance.

[oBFusCATed]

ThundThund: Have you tried the debugger's branch nightly? Also have you read this http://wiki.codeblocks.org/index.php?title=Debugging_with_Code::Blocks ?

[ThundThund]

I've not tried that branch. I'm going to read that just in case I forgot something.

[ThundThund]

I achieve all the requirements of the article.

[zabzonk]

@oBFusCATed

Did you try the small code sample I posted? Does it work for you? For me it doesn't even stop after the assert using command-line gdb; does it for you?

[oBFusCATed]

Code Select Expand


int main() {
BOOST_ASSERT(false);
...
}

Works flawlessly.

[zabzonk]

Yes, but does the code I posted work flawlessly?

[oBFusCATed]

Yes, the same as with my code...

[zabzonk]

Could you post a screenshot? I suspect that what you class as working and what I and the OP class as working may be different.

[ThundThund]

What exactly do you need I show in the screenshot?

[zabzonk]

Sorry I meant:

@oBFusCATed

Could you post a screenshot? I suspect that what you class as working and what I and the OP class as working may be different.


You (i.e. ThundThund) are the OP == Original Poster

[oBFusCATed]

Hm, why do you need a screen shot? It is the same as if the debugger is stopped on a breakpoint...

And keep in mind that I'm on linux and I'm running the latest debugger branch code. I don't know what is the behaviour of the 10.05 or trunk.

[zabzonk]

@oBFusCATed

I'd like to see  screenshot so that I can see what you think the correct appearance of the system should be after the boost assert fails. For me it does seem to break in the debugger, but I don't know how you or the OP think this break should correctly be displayed.  My understanding of WX/scintilla is that the appearance should be more or less platform independent, so a screenshot from a working CB implementation should resolve this. And it will take you, what? - two minutes to do?

To be explicit, I'd like to see the debugger call stack window and the editor window.

[ThundThund]

I agree, it takes a few seconds to do and could clarify some things  .

[oBFusCATed]

http://smrt.is-a-geek.org/codeblocks/screens/break_on_assert.png happy?