Add debug support #4

sago35 · 2022-02-14T07:59:07Z

This PR adds debug support to vscode-tinygo.
It works as follows.

Add some definitions to .vscode/settings.json
Add settings for debug launch to .vscode/launch.json
- With this configuration, pressing F5 will launch the debugger with TinyGo configured.
Add build tasks to .vscode/tasks.json to be used from .vscode/launch.json

The following are the parts that are not done so far.

~~If tasks.json does not exist, adding a task will fail.~~ fixed
- ~~If you create the file to be written later first, there will be no error.~~
This is my first time using typescript, so I'm not sure if I'm writing the right code.

sago35 · 2022-02-14T08:12:35Z

Use it this way for now.
If there is a better way, I'd like your opinion.

https://www.youtube.com/watch?v=omT0agnFHA4

sago35 · 2022-02-14T09:57:56Z

I forgot to write.
In order to run it, you will need tinygo from the following branch

https://github.com/tinygo-org/tinygo/tree/buildinfo

sago35 · 2022-02-16T10:11:53Z

It is now possible to easily launch a debugger using VSCode.
If you run tinygo target on the screen where the main package to be debugged is open, the various settings will be updated.
After that, press F5 to execute the build and start debugging.

Right now, only openocd is supported.
However, the openocdInterface can be changed

bmentink · 2022-03-14T02:18:39Z

@sago35
HI, could you please write a quick HOWTO of getting VSCode debugging going for a RP Pico target? I have another RP Pico programmed as a USB->SWD that I can use for the hardware interface, I also have an openocd that supports that target. WHat scripts will I need for VSCode to connect gdb/openocd etc ..

Cherrs

sago35 · 2022-03-14T10:12:08Z

@bmentink
First you must be able to run tinygo flash with picoprobe.

openocd must support picoprobe.
You can use the official raspberrypi one or the following.

https://github.com/ciniml/debug-tools-builder/releases/

$ tinygo flash --target pico --size short --programmer picoprobe examples/blinky1
   code    data     bss |   flash     ram
   5704       4    2264 |    5708    2268
Open On-Chip Debugger 0.11.0-rc2+dev-gcafa0b5 (2021-02-20-22:09)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'swd'
Warn : Transport "swd" was already selected
adapter speed: 5000 kHz

Warn : Transport "swd" was already selected
swd
Info : Hardware thread awareness created
Info : Hardware thread awareness created
Info : RP2040 Flash Bank Command
Info : clock speed 5000 kHz
Info : SWD DPIDR 0x0bc12477
Info : SWD DLPIDR 0x00000001
Info : SWD DPIDR 0x0bc12477
Info : SWD DLPIDR 0x10000001
Info : rp2040.core0: hardware has 4 breakpoints, 2 watchpoints
Info : rp2040.core1: hardware has 4 breakpoints, 2 watchpoints
Info : starting gdb server for rp2040.core0 on 3333
Info : Listening on port 3333 for gdb connections
target halted due to debug-request, current mode: Thread
xPSR: 0xf1000000 pc: 0x000000ee msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0xf1000000 pc: 0x000000ee msp: 0x20041f00
** Programming Started **
Info : RP2040 B0 Flash Probe: 2097152 bytes @10000000, in 512 sectors

target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
Info : Writing 8192 bytes starting at 0x0
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
** Programming Finished **
** Resetting Target **
shutdown command invoked

If you can tinygo flash, next you need to check tinygo gdb.
Make sure tinygo gdb is running correctly by using continue, etc.

$ tinygo gdb --target pico --size short --programmer picoprobe examples/blinky1

Next you need to build tinygo at buildinfo branch.
It is OK if JSON is output by executing the following command.

https://github.com/tinygo-org/tinygo/tree/buildinfo

$ tinygo build -json --target pico --size short --programmer picoprobe examples/blinky1
{
  "Options": {
    ...
  },
  "Target": {
    ...
  },
  "GoMinorVersion": 17,
  "ClangHeaders": "C:\\tinygo\\tinygo\\llvm-project\\clang\\lib\\Headers",
  "TestConfig": {
    "CompileTestBinary": false
  }
}

sago35 · 2022-03-14T11:37:40Z

Openocd Interface must be configured.

bmentink · 2022-03-15T00:57:06Z

Many Thanks. Regarding the "building tinygo" step. I am using your custom branch that has the PWM max frequency fix, has that been applied to the buildinfo branch ?

@sago35 .. Also, what is the extension name that gives you the vscode picoprobe openocd interface? I only see one for MacOS and I am on Linux .... or does it work for Linux as well .. (My TinyGo extension does not have any options you can set)

bmentink · 2022-03-18T02:56:17Z

@sago35 I have picoprobe flashing and gdb talking to the board. I just need further help with setting up visualStudio. Thanks.
Maybe you can be more specific with the steps, what extension to load, what JSON file to use .. etc i.e launch.json

sago35 · 2022-03-18T03:24:56Z

Now you can use the vsce package command to create an extension for this branch version.

Once created, install the extension.
You only need to configure openocd interface for vscode.

Subsequent steps are as shown in the video below.
https://twitter.com/sago35tk/status/1503330468707860481

note:
It is not necessary to create launch.json, etc., as they are generated by the extension.

bmentink · 2022-03-21T01:28:58Z

@sago35
I can't use the buildinfo branch unless you have applied the patch for the PWM max freqency fix ... I ask again, have you?
If not, how can I patch the buildinf branch with the PWM fix ..?

Is the vsce package command only available in the buildinfo branch as I don't see it anywhere ..

sago35 · 2022-03-21T01:36:44Z

@bmentink
In most cases, it should be a simple matter to do the following

$ git checkout buildinfo
$ git rebase  YOUR_BRANCH_NAME
$ make llvm-build && make
$ ./build/tinygo version

Is the vsce package command only available in the buildinfo branch as I don't see it anywhere ..

vsce is for VSCode.
In other words, it is for tinygo-org/vscode-tinygo.

https://code.visualstudio.com/api/working-with-extensions/publishing-extension

bmentink · 2022-03-21T01:42:12Z

I don't have vsce installed, do I have to install that with npm? You say vsce is for VSCode but I see from the link above, that vsce is Video Studio code EXTENSION to manage extensions. I have vscode but not vsce ... I am confused.

Please give clear steps on what to do with visual to get the extension .. i.e treat me like a baby :)

sago35 · 2022-03-21T01:54:14Z

@bmentink

Please wait a moment while I upload the vsix file.
If you are in a hurry, do the following

First, Node.js must be installed.
After that, vsce must be installed with the following command.

https://code.visualstudio.com/api/working-with-extensions/publishing-extension
Installation
Make sure you have Node.js installed. Then run:

$ npm install -g vsce

Now all that remains is to run the following to create vscode-tinygo-<version>.vsix.

https://github.com/tinygo-org/vscode-tinygo#development

To create an extension as a package, run the following command:
vsce package
This creates a new vscode-tinygo-.vsix file that you can install directly in VS Code.

$ git clone https://github.com/tinygo-org/vscode-tinygo
$ cd vscode-tinygo
$ git checkout gdb
$ vsce package

bmentink · 2022-03-21T01:56:33Z

Perfect .. Thanks 👍

sago35 · 2022-03-21T02:06:55Z

@bmentink
Unzip the following zip file and load it into vscode.

vscode-tinygo-0.3.0-dev1.vsix.zip

bmentink · 2022-03-21T03:10:07Z

I have the extension installed, and I have selected the openocd interface. However the settings.json file and the tasks.json files look wrong, as this is what I get when trying to run a debug session.

The terminal process "/usr/bin/bash '-c', 'tinygo build -o /out.elf -target pico -size short -opt 1 ./bldc'" terminated with exit code: 2.

Am I not mean't to edit those files with the correct paths etc ..?

sago35 · 2022-03-21T03:47:13Z

@bmentink
Please rename or delete the .vscode directory and try again.

bmentink · 2022-03-21T20:02:44Z

@sago35 I tried what you suggested, I removed .vscode, and reinstalled go and the .vsix file as you suggested. the paths still took wrong.

tasks.json looks like:

{
	"version": "2.0.0",
	"tasks": [
		{
			"label": "tinygo build task",
			"type": "shell",
			"command": "tinygo build -o ${env:TMP}/out.elf -target ${config:go.toolsEnvVars.TARGET} -size short -opt 1 ${config:go.toolsEnvVars.TargetPkg}",
			"problemMatcher": [],
			"group": {
				"kind": "build",
				"isDefault": true
			}
		}
	]
}

The error was:

panic: expected main package to have name 'main'

goroutine 1 [running]:
github.com/tinygo-org/tinygo/loader.(*Package).Check(0xc0003b7dc0)
        /home/runner/work/tinygo/tinygo/loader/loader.go:373 +0x318
github.com/tinygo-org/tinygo/loader.(*Program).Parse(0xc00026c0c0)
        /home/runner/work/tinygo/tinygo/loader/loader.go:299 +0xb9
github.com/tinygo-org/tinygo/builder.Build({0x7fff4f07669d, 0x6}, {0x7fff4f076674, 0x60}, 0xc00023e510, 0xc004d0b7e0)
        /home/runner/work/tinygo/tinygo/builder/build.go:177 +0xfa9
main.Build({0x7fff4f07669d, 0x6}, {0x7fff4f076674, 0x8}, 0x1)
        /home/runner/work/tinygo/tinygo/main.go:151 +0x8f
main.main()
        /home/runner/work/tinygo/tinygo/main.go:1337 +0x3aed
The terminal process "/usr/bin/bash '-c', 'tinygo build -o /out.elf -target pico -size short -opt 1 ./bldc'" terminated with exit code: 2.

Terminal will be reused by tasks, press any key to close it.2.

It seems to have ignored me setting the tinygo path to my custom build tinygo ... The tinygo path in my case is: ~/tinygo/build/tinygo

For reference, my settings.json looks like:

{
    "go.toolsEnvVars": {
        "GOROOT": "/home/bmentink/.cache/tinygo/goroot-69d4dd4e42b0c20ced8e32cfa58b0593ee5a356c354f3328202260d070e3e317",
        "GOFLAGS": "-tags=cortexm,baremetal,linux,arm,rp2040,rp,pico,tinygo,math_big_pure_go,gc.conservative,scheduler.tasks,serial.uart",
        "TARGET": "pico",
        "TINYGOROOT": "/home/bmentink/tinygo/build/tinygo",
        "GdbPath": "",
        "OpenocdInterface": "picoprobe",
        "OpenocdTarget": "",
        "X01": "/home/bmentink/Code/tinygo_BLDC_M3_180deg_soft",
        "TargetPkg": "./bldc"
    }
}

bmentink · 2022-03-21T22:35:50Z

Ahhh, I missed setting the target when the window containing main() is open ... very important step !!!! ...
Now I have a permission error as I usually have to run tinygo with sudo ...

tinygo:ld.lld: error: cannot open /usr/local/lib/tinygo/pkg/thumbv6m-unknown-unknown-eabi-cortex-m0plus/compiler-rt/lib.a: Permission denied
tinygo:ld.lld: error: cannot open /usr/local/lib/tinygo/pkg/thumbv6m-unknown-unknown-eabi-cortex-m0plus/picolibc/lib.a: Permission denied

sago35 · 2022-03-21T22:36:47Z

@bmentink

panic: expected main package to have name 'main'

When starting debug, run it while the main package is displayed in VSCode.

Also, please let me know the results of the following command so I can look into it.
If the package name (./bldc) is incorrect, please provide the correct value.

$ tinygo build -json -o /out.elf -target pico -size short -opt 1 ./bldc

bmentink · 2022-03-21T22:46:56Z

What do you mean by package name?, In my source directory (where main.go is) there is also a sub-directory called bldc, maybe it is getting confused?

The out put of the above command is:

{
  "Options": {
    "GOOS": "linux",
    "GOARCH": "amd64",
    "GOARM": "6",
    "Target": "pico",
    "Opt": "1",
    "GC": "",
    "PanicStrategy": "print",
    "Scheduler": "",
    "Serial": "",
    "PrintIR": false,
    "DumpSSA": false,
    "VerifyIR": false,
    "Debug": true,
    "PrintSizes": "short",
    "PrintAllocs": null,
    "PrintStacks": false,
    "Tags": "",
    "WasmAbi": "",
    "GlobalValues": {},
    "TestConfig": {
      "CompileTestBinary": false
    },
    "Programmer": "",
    "OpenOCDCommands": null,
    "LLVMFeatures": "",
    "Directory": "",
    "PrintJSON": true
  },
  "Target": {
    "inherits": [
      "cortex-m",
      "cortex-m0plus",
      "rp2040"
    ],
    "llvm-target": "thumbv6m-unknown-unknown-eabi",
    "cpu": "cortex-m0plus",
    "features": "+armv6-m,+soft-float,+strict-align,+thumb-mode,-aes,-bf16,-cdecp0,-cdecp1,-cdecp2,-cdecp3,-cdecp4,-cdecp5,-cdecp6,-cdecp7,-crc,-crypto,-d32,-dotprod,-dsp,-fp-armv8,-fp-armv8d16,-fp-armv8d16sp,-fp-armv8sp,-fp16,-fp16fml,-fp64,-fpregs,-fullfp16,-hwdiv,-hwdiv-arm,-i8mm,-lob,-mve,-mve.fp,-neon,-ras,-sb,-sha2,-vfp2,-vfp2sp,-vfp3,-vfp3d16,-vfp3d16sp,-vfp3sp,-vfp4,-vfp4d16,-vfp4d16sp,-vfp4sp",
    "goos": "linux",
    "goarch": "arm",
    "build-tags": [
      "cortexm",
      "baremetal",
      "linux",
      "arm",
      "rp2040",
      "rp",
      "pico"
    ],
    "gc": "conservative",
    "scheduler": "tasks",
    "serial": "uart",
    "linker": "ld.lld",
    "rtlib": "compiler-rt",
    "libc": "picolibc",
    "automatic-stack-size": true,
    "default-stack-size": 2048,
    "cflags": [
      "-Werror",
      "-fshort-enums",
      "-fomit-frame-pointer",
      "-mfloat-abi=soft",
      "-fno-exceptions",
      "-fno-unwind-tables",
      "-ffunction-sections",
      "-fdata-sections"
    ],
    "ldflags": [
      "--emit-relocs",
      "--gc-sections"
    ],
    "linkerscript": "targets/pico.ld",
    "extra-files": [
      "src/device/arm/cortexm.s",
      "src/internal/task/task_stack_cortexm.S",
      "src/runtime/gc_arm.S",
      "src/device/rp/rp2040.s",
      "targets/pico-boot-stage2.S"
    ],
    "rp2040-boot-patch": true,
    "emulator": null,
    "flash-command": "",
    "gdb": [
      "gdb-multiarch",
      "arm-none-eabi-gdb"
    ],
    "flash-1200-bps-reset": "",
    "serial-port": null,
    "flash-method": "msd",
    "msd-volume-name": "RPI-RP2",
    "msd-firmware-name": "firmware.uf2",
    "uf2-family-id": "0xe48bff56",
    "binary-format": "uf2",
    "openocd-interface": "",
    "openocd-target": "rp2040",
    "openocd-transport": "swd",
    "openocd-commands": null,
    "jlink-device": "",
    "code-model": "",
    "relocation-model": "",
    "wasm-abi": ""
  },
  "GoMinorVersion": 17,
  "ClangHeaders": "/home/bmentink/tinygo/llvm-project/clang/lib/Headers",
  "TestConfig": {
    "CompileTestBinary": false
  }
}

bmentink · 2022-03-21T22:50:36Z

If by package, you mean main.go, then the above command should be ..
tinygo build -json -o /out.elf -target pico -size short -opt 1 main.go ?

bmentink · 2022-03-21T22:52:36Z

At the moment, I am getting a permission error where it is compiling the .elf file:

error: open /out.elf: permission denied
The terminal process "/usr/bin/bash '-c', 'tinygo build -o /out.elf -target pico -size short -opt 1 ./.'" terminated with exit code: 1.

why is there a "/" in front of the out.elf?

sago35 · 2022-03-21T22:52:44Z

I think the ~~tinygo build~~ tinygo build -json results are fine.

update: change tinygo build to tinygo build -json

bmentink · 2022-03-21T22:53:33Z

Please see post.. https://github.com/tinygo-org/vscode-tinygo/pull/4#issuecomment-1074499084

bmentink · 2022-03-22T03:30:54Z

Adding the rules did not help ... will investigate further.. cheers

sago35 · 2022-03-22T03:31:29Z

Can tinygo gdb run at this point?
Will openocd work from tinygo gdb?

bmentink · 2022-03-22T03:33:44Z

tinygo gdb has always worked. How do I add openocd to the tinygo gdb command?

sago35 · 2022-03-22T03:35:11Z

When tinygo gdb is run, openocd is also run.
Try adding the -x option to tinygo gdb.

sago35 · 2022-03-22T03:36:48Z

Adding -ocd-output would make it clearer.

sago35 · 2022-03-22T03:44:08Z

You may try rebooting linux once.

bmentink · 2022-03-22T03:54:03Z

Ok, will try tomorrow.. Stopping for the day.. Thanks for the help..

…

On Tue, 22 Mar 2022, 4:44 pm sago35, ***@***.***> wrote: You may try rebooting linux once. — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACNHVB4EUOZMN7BNXLYL773VBE6ZFANCNFSM5OKUPISQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

bmentink · 2022-03-22T19:27:39Z

tinygo gdb -x -ocd-output shows everything working normally ..

bmentink · 2022-03-22T19:56:48Z

Yay, got it working. I discovered openocd requires you to be part of the plugdev group as well ... just dialout is not enough ..

sago35 · 2022-03-24T12:05:51Z

To complete this PR, the remaining tasks are as follows

Locate tmpdir using a method other than the $TMP environment variable
Delete the debugging key named X01
Add the following settings to settings.json
- cortex-debug.armToolchainPath
- cortex-debug.gdbPath
Add dependency settings for cortex-debug
~~Mention that binutils-arm-none-eabi is required even when using gdb-multiarch~~ No action required.
~~Get the location of the svd file from tinygo build -json~~
- ~~To do this, the tinygo command must be changed~~
- Once support is stopped because non tinygo developers don't have the svd files

sago35 · 2022-03-24T13:17:35Z

20220324_vscode-tinygo-0.3.0-dev1.vsix.zip

sago35 · 2022-03-24T13:22:07Z

No more $TMP setup, etc.
It is really easy to start the debugger.

Now ready for reaview.

bmentink · 2022-03-26T00:20:57Z

Great job!

@sago35 Have you tried debugging into interrupt handlers, or functions called from the handler? I can only seem to debug mainline code, which is frustrating, as all my code runs off interrupts ...

sago35 · 2022-03-26T03:25:03Z

@bmentink

I tried this with feather-m4-can.
It is possible to set break even for interrupts.
However, it is not comfortable to use.

I think we need better debugging support for tinygo, not just for interrupts.
Please create an issue at tinygo.org/tinygo.

sago35 · 2022-06-13T11:34:27Z

@aykevl
gdb branch rebased to 0.3.0.
Now ready for review.

By the way, the 0.3.0 tag does not seem to have been pushed.

sago35 · 2022-06-13T11:36:08Z

Pre-built binaries can be downloaded from the following links
vscode-tinygo-0.4.0-dev1.vsix.zip

sago35 · 2022-08-31T23:34:10Z

ping @aykevl

sago35 · 2022-08-31T23:36:43Z

If this PR takes a long time to review, I would like to see #6 released. @aykevl

aykevl

First review.

It looks like you are first building a binary using tinygo build and then debugging it separately using the Cortex-M debug extension, correct?
I think there is a better way, but I haven't investigated it yet: by using tinygo gdb directly and providing the gdb-rsp port number to the debugger. This will make it possible to debug all architectures, not just Cortex-M.
(Right now tinygo gdb will run GDB itself, but it could be modified to simply output the openocd port number that a VS Code extension could attach to).

aykevl · 2022-08-20T14:46:36Z

package.json

+				"tinygo.openocdInterface": {
+					"description": "which hardware programmer to use (ex: jlink, cmsis-dap, stlink-v2, ...)",
+					"type": "string",
+					"default": "cmsis-dap"


I think this should be an empty string by default, for boards that have an on-board debugger. For example, the BBC micro:bit has a cmsis-dap debugger on board while many STM32 development boards have a ST-Link debugger on board. By picking a debugger here, it looks like you are overriding the default for a particular board.

aykevl · 2022-09-15T11:06:03Z

src/extension.ts

+		let buildPkg = '';
+		let editor = vscode.window.activeTextEditor;
+		if (editor) {
+			buildPkg = editor.document.fileName;
+		}


Go packages normally work in packages, not in files. I think this should use the directory of the current file, not the path of the current file.

aykevl · 2022-09-15T11:10:01Z

src/extension.ts

+		envVars.TARGET = target;
+		envVars.TINYGOROOT = tinygoroot;
+		envVars.GdbPath = path.basename(gdbPath);
+		envVars.OpenocdInterface = openocdInterface;
+		envVars.OpenocdTarget = openocdTarget;
+		envVars.TmpDir = os.tmpdir();


Why are you storing all of these in .vscode/settings.json? I don't see how they are necessary for the Go extension.

sago35 · 2022-09-15T11:40:51Z

@aykevl Thanks for the review.

I think there is a better way, but I haven't investigated it yet: by using tinygo gdb directly and providing the gdb-rsp port number to the debugger. This will make it possible to debug all architectures, not just Cortex-M.

I think that is a very good idea.
I will give it a try.
This would remove most of the envVars.

aykevl · 2022-09-15T15:37:21Z

If you didn't see it already, this will be useful: https://code.visualstudio.com/api/extension-guides/debugger-extension (I didn't read the page yet).

sago35 mentioned this pull request Feb 14, 2022

is there a plan for debug adapter feature for vsc,it's useful. #3

Open

sago35 force-pushed the gdb branch from f3304d1 to 6890c85 Compare February 16, 2022 10:11

sago35 marked this pull request as ready for review February 16, 2022 10:12

aykevl mentioned this pull request Mar 1, 2022

panic when Interrupts enabled in RP Pico tinygo-org/tinygo#2653

Closed

sago35 mentioned this pull request Mar 14, 2022

build: add JSON output to build command tinygo-org/tinygo#2712

Merged

sago35 marked this pull request as draft March 24, 2022 12:00

sago35 marked this pull request as ready for review March 24, 2022 13:22

sago35 requested a review from aykevl March 24, 2022 13:22

sago35 mentioned this pull request Jun 2, 2022

Revisting 1157 - Adding delve support for TinyGo tinygo-org/tinygo#2888

Open

sago35 force-pushed the gdb branch from ed66c5e to 5e49230 Compare June 13, 2022 09:29

sago35 marked this pull request as draft June 13, 2022 09:33

Add support for debug

c3141d4

sago35 force-pushed the gdb branch from 5e49230 to c3141d4 Compare June 13, 2022 11:32

sago35 marked this pull request as ready for review June 13, 2022 11:32

aykevl reviewed Sep 15, 2022

View reviewed changes

Add debug support #4

Are you sure you want to change the base?

Add debug support #4

Conversation

sago35 commented Feb 14, 2022 • edited

sago35 commented Feb 14, 2022 • edited

sago35 commented Feb 14, 2022

sago35 commented Feb 16, 2022

bmentink commented Mar 14, 2022

sago35 commented Mar 14, 2022

sago35 commented Mar 14, 2022

bmentink commented Mar 15, 2022 • edited

bmentink commented Mar 18, 2022 • edited

sago35 commented Mar 18, 2022 • edited

bmentink commented Mar 21, 2022 • edited

sago35 commented Mar 21, 2022

bmentink commented Mar 21, 2022 • edited

sago35 commented Mar 21, 2022

bmentink commented Mar 21, 2022

sago35 commented Mar 21, 2022

bmentink commented Mar 21, 2022 • edited

sago35 commented Mar 21, 2022

bmentink commented Mar 21, 2022 • edited

bmentink commented Mar 21, 2022 • edited

sago35 commented Mar 21, 2022

bmentink commented Mar 21, 2022

bmentink commented Mar 21, 2022

bmentink commented Mar 21, 2022

sago35 commented Mar 21, 2022 • edited

bmentink commented Mar 21, 2022

bmentink commented Mar 22, 2022

sago35 commented Mar 22, 2022 • edited

bmentink commented Mar 22, 2022

sago35 commented Mar 22, 2022

sago35 commented Mar 22, 2022

sago35 commented Mar 22, 2022

bmentink commented Mar 22, 2022 via email

bmentink commented Mar 22, 2022

bmentink commented Mar 22, 2022

sago35 commented Mar 24, 2022 • edited

sago35 commented Mar 24, 2022

sago35 commented Mar 24, 2022

bmentink commented Mar 26, 2022

sago35 commented Mar 26, 2022

sago35 commented Jun 13, 2022

sago35 commented Jun 13, 2022

sago35 commented Aug 31, 2022

sago35 commented Aug 31, 2022

aykevl left a comment

Choose a reason for hiding this comment

aykevl Aug 20, 2022

Choose a reason for hiding this comment

aykevl Sep 15, 2022

Choose a reason for hiding this comment

aykevl Sep 15, 2022

Choose a reason for hiding this comment

sago35 commented Sep 15, 2022

aykevl commented Sep 15, 2022

sago35 commented Feb 14, 2022 •

edited

sago35 commented Feb 14, 2022 •

edited

bmentink commented Mar 15, 2022 •

edited

bmentink commented Mar 18, 2022 •

edited

sago35 commented Mar 18, 2022 •

edited

bmentink commented Mar 21, 2022 •

edited

bmentink commented Mar 21, 2022 •

edited

bmentink commented Mar 21, 2022 •

edited

bmentink commented Mar 21, 2022 •

edited

bmentink commented Mar 21, 2022 •

edited

sago35 commented Mar 21, 2022 •

edited

sago35 commented Mar 22, 2022 •

edited

sago35 commented Mar 24, 2022 •

edited