Tagged with: go — Alex Carney

TIL: Debugging go programs with gdb

$ gdb --args podman info
(gdb) run
Starting program: /usr/bin/podman info
[Thread debugging using libthread_db enabled]
...
WARN[0000] Found incomplete layer "6748b9a4e6f2d75763acd0d8351dfb92d4281a0b3546cc68042fb8cb5e1b7c3c", deleting it

Thread 9 "podman" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fbacbfff6c0 (LWP 10496)]
Downloading source file /usr/src/debug/podman-5.3.1-1.fc41.x86_64/vendor/github.com/containers/storage/layers.go
github.com/containers/storage.(*layerStore).load (r=0xc00024c140, lockedForWriting=true, ~r0=<optimized out>, ~r0=<optimized out>, ~r1=..., ~r1=...) at /usr/src/debug/podman-5.3.1-1.fc41.x86_64/vendor/github.com/containers/storage/layers.go:917
917                     if layer.Flags == nil {

<Freeze frame, record scratch>

You might be wondering how I got here…

And no, I wasn’t trying to work on podman!

Passing strings between TinyGo and JavaScript

After getting a "Hello, World!" WebAssembly application working I thought it would be fun to try and implement a toy programming language in the browser. However before I could even start thinking about parsers, abstract syntax trees and the like I had to be able to pass strings between my WebAssembly module and the surrounding JavaScript.

Turns out that is much trickier than I expected.

Saying ‘Hello, World!’ with TinyGo and WebAssembly

WebAssembly is something I’ve wanted to play with for quite a while now and I’ve finally got around to taking a look at it. In this post I describe how I managed to use TinyGo to compile a “Hello, World!” Go program into WebAssembly and execute it in the browser. So that I have something to refer back to I also describe setting up my development environment as a container using LXD.