For$
<!-- begin site header -->
<div id=

Author Topic: Unable to debug under windows; Suggestions?  (Read 5188 times)

Odium

  • Newbie
  • *
  • Posts: 19
    • View Profile
Unable to debug under windows; Suggestions?
« on: April 17, 2011, 07:39:35 am »
So, using a fresh buildpack and VS2010 one is unable to debug.
Seeing as there's a lack of info on the wiki or elsewhere regarding anything to do with mineserver and windows I'm somewhat at a loss as to how to continue.
(one can still compile etc, the user is simply unable to debug, which is becoming more and more a rather annoying drawback)

on compile the user is presented with about a dozen 'warnings' as the one's below (not just a doezen, there's a few hundred, however these are the only one's that are relevant to the current issue)
-----
libevent.lib(event.obj) : warning LNK4099: PDB 'vc100.pdb' was not found with
'libevent.lib(event.obj)' or at 'C:\Fresh_Build\mineserver\bin\vc100.pdb'; linking object as if no debug info

On attempting to debug user is presented with the below errors and once again about a dozen or more similar to those containing 'cannot find or open the PDB file
-----
'mineserver.exe': Loaded 'C:\Windows\System32\usp10.dll', Cannot find or open the PDB file
'mineserver.exe': Loaded 'C:\Fresh_Build\mineserver\bin\libnoise.dll', Binary was not built with debug information.
'mineserver.exe': Loaded 'C:\Fresh_Build\mineserver\bin\zlibwapi.dll', Binary was not built with debug information.

is anyone able to suggest a cause / fix for the above issue?

Satome

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: Unable to debug under windows; Suggestions?
« Reply #1 on: April 19, 2011, 04:44:52 am »
Set the working directory for debugging, since it's not set to ../bin in the default settings.
You can set it in project property page -> configuration properties -> debugging

louisdx

  • Newbie
  • *
  • Posts: 12
    • View Profile
Re: Unable to debug under windows; Suggestions?
« Reply #2 on: April 19, 2011, 02:13:55 pm »
Please attach a backtrace once you get the program to crash inside your debugger. Then we'll be able to see where the problem originates.