• Advertisement
  • entries
    359
  • comments
    237
  • views
    189011

I am a fibber.

Sign in to follow this  

123 views

None of those things ended up implemented... instead, I ran through the Path serialization infrastructure and added flags to catch wrapping maps [more difficult than usual due to client ignorance of map size].



During debugging work, I managed to trigger a few, non-reproducable access violations in C#. The line in question:

font.DrawText(null, SrcText(), tblr.fetch(), Format, Color);


looks innocent enough. This of course makes me fear for my life. Randomish errors like that in C++ were often some nasty overrun bug, or a subtle timing issue. The parameters there don't change much, and certainly not anywhere there could be a timing issue. Does C# have overrun problems? I suspect so, though I'd be hard pressed to guess where they could happen. I don't think it's a GC issue, as I've found a few of those and they lead to different errors... Maybe an internal MDX problem that will just drive me stark raving mad. *shrug* Hockey time.
Sign in to follow this  


0 Comments


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Advertisement