{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifqk2mfrmdemjwbz5aaklzcbq6xn3by5nll2jmui7kcfaozs2bvfq",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3me5d32nctrs2"
  },
  "path": "/viewtopic.php?t=33137&p=270098#p270098",
  "publishedAt": "2026-02-05T20:35:25.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> I didn't find anything specific written on the website regarding running Pale Moon under Visual Studio's debugger. Do you just build it according to usual instructions, run the browser, then use the attach to process option in Visual Studio?\n\nYeah if I actively debug code I build and mach run, with the symbol path set to the appropriate objdir in VS if it needs that (usually it finds them automatically), and attach the debugger to the running process. It just works grabbing any crashes or breakpoints. I use the same method investigating reported crash addresses (but then of course running release and pointing symbols paths to the release objdir)\n\n* * *",
  "title": "Browser Development • Re: Visual Studio 2026",
  "updatedAt": "2026-02-05T20:35:25.000Z"
}