tinyjo: (Default)
Sometimes, I really really hate VB.NET. I received a bug report yesterday that some things were becoming enabled when they shouldn't be. This morning, I started to investigate. Unfortunately, I can't, because if I put a breakpoint in the function which is supposed to disable the stuff it suddenly starts working properly and disabling them! Then I take it out and it stops working again. How am I supposed to figure out what's going on?

Date: July 10th, 2003 05:20 am (UTC)From: [identity profile] sparkymark.livejournal.com
Some race condition that stops happening when you only have one thread running at a time? That's how the VMS debugger "fixes" bugs for you anyway.

Date: July 10th, 2003 06:37 am (UTC)From: [identity profile] soulsong.livejournal.com
That's my favourite kind of bug.

Date: July 10th, 2003 06:37 am (UTC)From: [identity profile] phlebas.livejournal.com
Is it specifically when you breakpoint there, or whenever you run via the debugger? Memory initialisation can be an issue with things happening like that (though I don't know how it works in VB.N)

Date: July 10th, 2003 02:17 pm (UTC)From: [identity profile] celestialweasel.livejournal.com
Write statements stuffing stuff into files, like we did when I were a lad.

Profile

tinyjo: (Default)
Emptied of expectation. Relax.

June 2020

S M T W T F S
 1 23456
78910111213
14151617181920
21222324252627
282930    

Most Popular Tags

Expand Cut Tags

No cut tags
Page generated September 14th, 2025 03:57 pm
Powered by Dreamwidth Studios

Style Credit