quinzee.cloud

Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.

Developer’s guide

19. Debug your application and QHQ

Debug C# where its network configuration works

Keep source on the host and run the chapter 3 SDK container. Build with dotnet build --no-restore and run with dotnet run --no-restore. Your editor can attach to that development container using its normal C# debugging tools; keep the same SSL_CERT_FILE, DNS configuration and private settings mount. Do not move the process to the host and assume its Azure-name resolution is unchanged.

Start with breakpoints around the application operation that fails. Inspect status/error codes and resource names. Avoid copying token, connection-string or secret values out of the debugger. For the supplied web application, use its step status and trace ID to find the corresponding platform trace.

An application exception can occur after provisioning succeeded. Inspect resources before rerunning; an incremental deployment may safely reuse them, whereas cleanup deliberately removes data.

Debug QHQ with F5

In VS Code, install the C/C++ extension and GDB, open the repository and choose QHQ (Rasta) + quinzee.cloud (Docker). F5 builds QHQ and its viewer, prepares certificates and starts the default cloud environment. Breakpoints in src/qhq/ run against that instance, not automatically against the book's application environment.

Stopping that debugger session stops its viewer/environment while preserving its state. To manage the already-running application environment instead, use the QHQ chapter's explicit connection.

Debug the native cloud

Build a debug binary and run it under gdb --args with its explicit data and TLS paths as in native operation. Use a separate data directory for debugging; two cloud processes must not write the same state.

The HTTP demonstration server also supports make debug-up and make debug-down, with gdbserver on loopback port 2345. That program tests the transport library; it does not provide Azure services.