Add tip about debug overhead

[dev590t]

No description provided.

[rocky]

LGTM - there are small changes I'll make down the line, but for now this is good.

I will be out of town for a little more than a week.

[dev590t]

yeah, I close the issue #40

[rocky]

@dev590t Due to work in using this debugger for use in the open source Mathematica project, Mathics3, I have been working on this project recently, and have fixed several problems in the slowness around using "finish", "next", and "continue".

I have also gone over the document to explain the situation better. There is still some slowness compared to pdb. I am not completely sure what exactly is wrong or different. But the code is faster (and has fewer bugs in hangs).

[dev590t]

nice!

[rocky]

nice!

Nice, but it would be even better to figure out where the additional overhead is still coming from in trepan3k that isn't in pdb. Some callbacks to the debugger occur that it feels like should not be happening.

What's weird is that this code has way more information about the program at its disposal that pdb doesn't have. How to make even better use of it is still a mystery.