Q: I set a breakpoint and cannot start my image any more. How can I recover?
Problem
I set a breakpoint and cannot start my image any more. How can I recover?
The failure of the image to start maybe the result of a breakpoint that gets hit during the startup sequence.
Symptoms may include:
•"Exit due to error: 58 - Invalid image relocation".
•An error message dialog like the following:
The following error(s) were detected during the startup sequence which may interfere with correct operation:
1) Breakpoint #2
Do you wish to attempt to continue anyway?
Pressing "Yes" in that error message box does not open a window.
Solution
If you are using an image from Version 8.6.2 or later, introduce a .cnf file into your development environment which turns off the breakpoint manager during startup, then turns it back on after startup is completed.
The .cnf file can be placed in the startup directory. This is the directory from which the image is launched. In the development context, it is the directory where the image (.icx) and .ini files are found. In the context of Environments, the startup directory is also known as the 'environment folder'.
Here is the .cnf file
System image breakpointManager breakpointsEnabled: false.!
PostStartup!
System image breakpointManager breakpointsEnabled: true.!
If you are using an image before 8.6.2, you can still introduce a .cnf file which turns off the breakpoint manager during startup. However, you will have to manually enable the breakpoint manager after startup is completed.
Here is the .cnf file
System image breakpointManager breakpointsEnabled: false.!
Enable the breakpoint manager by executing the following Smalltalk expression once the image has started up.
System image breakpointManager breakpointsEnabled: true.
Last modified date: 03/17/2020