Wish: save breakpoints and load them into another image

[waynej]

I tend to run my development with a set of breakpoints. But when I need to start over with the generic abt.icx, I really wish I had the ability to load those breakpoints from my previous development image. Is there a way to do this?

[tc]

Hello,

I opened case 44203 to explore this.

--tc

[rjs]

Try the attached zip file. It is code from VisualAge Smalltalk 6.0.2, so it may not work correctly under VASmalltalk 8. However, it shouldn't take much to make it work, if it doesn't already.

Of course, you will need to add code to hook it up to the menus, etc.

Invoke

Code: Select all

System dumpAllBreakpoints

and

Code: Select all

System fileInBreakpoints

This code is free for anyone to use, in any way they desire, commercial or otherwise.
Attribution would be appreciated, of course.

[waynej]

Wow, rjs, this looks so very promising. I can file out breakpoints just fine in 6.0.2 and 8.0.0. However, in either one I can't file the breakpoints back in.

Doing 'System fileInBreakpoints', I hit:
EmSystemConfiguration does not understand fileIn:
indeed I have no implementors of #fileIn: in the image.
I suspect I should be able to open the breakpoint file in a workspace and file in the contents that way, but I hit:
DbgBreakpoint does not understand forMethod:watchString:parseNodeId:

Am I missing something?

[rjs]

Wow, rjs, this looks so very promising. I can file out breakpoints just fine in 6.0.2 and 8.0.0. However, in either one I can't file the breakpoints back in.

Am I missing something?

Yes, you are missing the code I neglected to include.
Some of the methods were in different applications and I overlooked them the fist time. Hopefully, breakpoints2.zip has everything you need.

As before, exercise it using:

Code: Select all

System dumpAllBreakpoints
System fileInBreakpoints


(I tested this in an 8.0.0 image this time, so you really should have everything you need now.)

[waynej]

Thanks! It works and is a wish come true.

No complaints here, I am simply documenting behavior:

If you have a breakpoint at a line where a filed-in breakpoint is to go, the pre-existing breakpoint "wins".

You will get a message like this in the Transcript if appropriate:
The current edition of ClassName>>#methodName (breakpoint #xx) has changed since the breakpoint was saved. It may not be in the correct location now.

If you file in breakpoints including one in a no-longer-existing method, you get a walkback and none of the later 'good' breakpoints take effect.

If you file in breakpoints including one in a no-longer-existing class, you get the Transcript shows 'compiler error "undefined"' and none of the 'good' breakpoints take effect.

Besides "System fileInBreakpoints", you can also bring up a Workspace on the .brk file and perform the 'File In' operation.

If you file out breakpoints with some of them disabled, when filed back in they will be active. This small caveat I fixed with the attached.

[jtzecher]

This code is free for anyone to use, in any way they desire, commercial or otherwise.
Attribution would be appreciated, of course.

I really like this tool. I am getting ready to load it into our development tools. To whom my I attribute it to?

[rjs]

This code is free for anyone to use, in any way they desire, commercial or otherwise.
Attribution would be appreciated, of course.

I really like this tool. I am getting ready to load it into our development tools. To whom my I attribute it to?

"rjs" would be sufficient, but "Richard Sargent" will also work.
Most important, I am glad it is proving useful.