title: Why won't my code segfault on Windows 7?
body: <p>This is an unusual question to ask but here goes:</p>
  
  <p>In my code, I accidentally dereference NULL somewhere. But instead of the application crashing with a segfault, it seems to stop execution of the current function and just return control back to the UI. This makes debugging difficult because I would normally like to be alerted to the crash so I can attach a debugger.</p>
  
  <p>What could be causing this?</p>
  
  <p>Specifically, my code is an ODBC Driver (ie. a DLL). My test application is ODBC Test (odbct32w.exe) which allows me to explicitly call the ODBC API functions in my DLL. When I call one of the functions which has a known segfault, instead of crashing the application, ODBC Test simply returns control to the UI without printing the result of the function call. I can then call any function in my driver again.</p>
  
  <p>I do know that technically the application calls the ODBC driver manager which loads and calls the functions in my driver. But that is beside the point as my segfault (or whatever is happening) causes the driver manager function to not return either (as evidenced by the application not printing a result).</p>
  
  <p>One of my co-workers with a similar machine experiences this same problem while another does not but we have not been able to determine any specific differences.</p>