user debugger window bad behaviors

[korli]

• the user debugger window isn't scrollable, thus making hard to view long

stacktraces.

• the user debugger keeps running when closing the user debugger window with the

top left Close button.

• the debugger() call in libroot.so doesn't bring up the user debugger as in R5.

[bonefish]

• We're still using the MiniTerminal since there were stability problems with

the real Terminal. You can display only the first n frames of a stack trace by "bt n", BTW.

• Mmh, OK, might be a MiniTerminal issue, too.
• I tested that with src/tests/servers/debug/crashing_app and it work fine

there. In what context did you experience that?

[korli]

• makes sense :)
• yes
• yes a test terminal app works fine. But some complex apps sometimes make a

call to BLooper::check_lock() which fails, debugger() is called and fails to bring the user debugger: I'll give you more details on how to reproduce this.

[korli]

I can't reproduce the third item, to be considered fixed.

[korli]

Considered closed as we moved to Terminal