Possible change to "run to line".

[epasveer]

Currently, "run to line" requires the target program to have already been started by 'run' or 'start'. However, Seer knows if the target program is running or not. If it's not running, I suppose it can intercept the "run to line" action and :

• Ensure target program is loaded.
• Set a temporary breakpoint at the "run to line" point.
• Start the target program and it would eventually stop at the breakpoint (and other breakpoints that may have been set).

From the user's perspective, the "run to line" would work regardless if the target program is running or not.

[awsdert]

Only just got seer running so the most I'm aware of regards options is --start & --run, I'm assuming you have the same function launching & it checks integer being more than 0 for breaking on main, why not make it treat that integer as a line & add a file parameter then you could add options like this: seer --file src/main.c --line 100 --start program [args]

[epasveer]

Seer has a button to save the current breakpoints to a file. Then, your next session, you can start Seer with with it.

% seer -b mybreakpoints.brk  --start program [args]

[epasveer]

But you have an interesting idea about creating a breakpoint from the command line when you run Seer. I'll give it some thought when I get to the task in this thread.

(I'm always looking for ideas/suggestions :^)

[epasveer]

Added a way to set a sourcefile:lineno breakpoint from the command line.

$ seergdb --bs hellofibonacci.cpp:28 hellofibonacci 1000

[epasveer]

This closes this task. Can be reopened or a new task can be created.

[awsdert]

Added a way to set a sourcefile:lineno breakpoint from the command line.

$ seergdb --bs hellofibonacci.cpp:28 hellofibonacci 1000```

Was the extra ``` at the end intentional or is that a markdown typo?

[epasveer]

Was the extra ``` at the end intentional or is that a markdown typo?

Sorry, a markdown typo. Thanks for letting me know.