#37 Log to file + commands at break point

[Pontus Berg]

1) I would very much like the option output the monitor output to file (general request)

Eg. d 1000 2000 >>file.txt

2) Also, in combination with breakpoints, I would like to see the option to execute a command (same as VICE function COMMAND does)

3) I would like an list of commands in a file to be this COMMAND reference.

So lets say I want to log all references to a filename when the program loads;

Set break point triggered when calling ffd5

The command that is executed at the triggering of the ffd5 break would be "m bb bc >>log.txt : m b7 >>log.txt" : x" (memory of the filename pointers, memory of filename length and then x from monitor and run the program again.

This way you can just play around with the program at will and it will build a log file for all the times where the logging criteria at met.

[slajerek]

1) Actually this works almost as you wrote: D 1000 2000 file.txt

Other points are interesting. I plan to add support to Vice monitor anyway that might fix this for you.

[Pontus Berg]

If that is the format, how does it tell if I want to append or create a new
file? (In standardio that is done using > vs >>)

/Pontus "Bacchus" Berg
FairLight concil...

Den tors 10 okt. 2019 kl 21:14 skrev slajerek slajerek@users.sourceforge.net:

1) Actually this works almost as you wrote: D 1000 2000 file.txt

Other points are interesting. I plan to add support to Vice monitor anyway
that might fix this for you.

---

• [tickets:#37] https://sourceforge.net/p/c64-debugger/tickets/37/ Log
  to file + commands at break point*

Status: open
Milestone: 1.0
Created: Sun May 05, 2019 12:03 AM UTC by Pontus Berg
Last Updated: Sun May 05, 2019 12:03 AM UTC
Owner: nobody

1) I would very much like the option output the monitor output to file
(general request)

Eg. d 1000 2000 >>file.txt

2) Also, in combination with breakpoints, I would like to see the option
to execute a command (same as VICE function COMMAND does)

3) I would like an list of commands in a file to be this COMMAND reference.

So lets say I want to log all references to a filename when the program
loads;

Set break point triggered when calling ffd5

The command that is executed at the triggering of the ffd5 break would be
"m bb bc >>log.txt : m b7 >>log.txt" : x" (memory of the filename pointers,
memory of filename length and then x from monitor and run the program again.

This way you can just play around with the program at will and it will
build a log file for all the times where the logging criteria at met.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/c64-debugger/tickets/37/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[slajerek]

It is just creating a new file, good point about > vs >>