Hello, The reason seems to be that the mechanism uses a âonceâ breakpoint which is for now implemented by removing the breakpoint at runtime. This leads to the debugger getting text/bytecode offset wrong as we install a different method. runTest: testSelector of: testClass | breakpoint | breakpoint := Breakpoint new node: (testClass lookupSelector: testSelector) ast; once; install. [super runTest: testSelector of: testClass] ensure: [ breakpoint remove ] I am thinking of implementing the once breakpoints using a condition instead (so that the byte code is unchanged). The other nice effect is that one can more easily re-enable those breakpoints (like haltOnce). As workaround, we can remove the âonceâ⦠as we remove the breakpoint in the ensure:, it should be removed and not stay around causing problems. (but it is there in case you would run the test again, that is why a once break is nicer). Marcus
On 15 Jun 2018, at 12:18, Marcus Denker <marcus.denker@inria.fr> wrote:
Thanks, I made a note and will look (I hope next week)
On 15 Jun 2018, at 01:07, Ben Coman <btc@openinworld.com> wrote:
Not sure if this is intended behaviour...
in a brand new build 71053, open a browser GTGenericStackDebuggerTest >> testBasic
right-click and choose "Debug"
the debugger opens about on the third statement. Clicking <Restart> doesn't improve things, and then clicking <Into> shows the stack on MetaLink>>uninstall.
cheers -ben