One of the things I love about this industry is that there is always more you can learn.

Running x64 is meaning I am hitting a few hurdles which result me having to figure out whats gone wrong and thus I end up learning something new.

Todays lesson is debugging, t86he tool I am writing this blog post is an extension I've written for Omea. Omea is an information application, it does RSS, NNTP and with my extension blogging. It will also index your files, outlook etc a bit like google desktop.

For some reason when I try and attach to Omea to debug my component it would attach but not do anything. not even load any symbols. Today I tried again and found that the "Attach to Process" dialog has a "Attach to" option this is the type of code you want to debug, x86, managed, TSQL or script. It was set to automatic, which means it detects what to debug. Oddly for OmeaPro.exe the type is Script, Managed x86, which seems to mean that the automatic debug type is script. Obviously not good as I want debug my managed code. So I manually selected Managed by clicking on the "Select ..." button and heh presto all the symbols are loaded and my breakpoints get hit.

I don't why the automatic doesn't detect the correct type, just another x64 feature :)


This is cross posted from my SQLBlogcasts blog which can be found here, http://sqlblogcasts.com/blogs/simons/Debugging on x64 machine

Categories:

Add comment


(Will show your Gravatar icon)  

  Country flag

biuquote
  • Comment
  • Preview
Loading



Theme design by Nukeation based on Jelle Druyts