Sorry I were forgot about that you don't have MSVC++ 2005 on the work PC.
So I don't think that any GNU debugger have option to attach to proccess when the process is already running, you need to start CS with the debuger. I don't know how is the UI of Code::Blocks but maybe it have something like Debug menu with option to start an executable file. To debug CS in that way you must create file SteamApp.cfg in to the
Steam\SteamApps\account_name\counter-strike\
folder.
The File must looks like that:
Quote:
################################################## ##########################
##
# SteamApp.cfg
#
# Steam Client App configuration-override file
#
# This file is read by the Steam code in the Client
# Application, and controls configurable parameters that
# affect only that App.
#
# To be effective it must be placed in the App directory
# (for example, c:\Steam\SteamApps\me@web.com\Half-Life\).
#
################################################## ##########################
##
#
# Debug-launch settings
#
# Use these settings when you are running your application directly
# from your debugger (ie, not launching the App from the Steam UI)
# In such cases, you need to tell Steam which application
# you are running and the version you want to use. Each application has
# an ID number and each version of your application has a version ID number.
# You also need to indicate the username you are running Steam under.
#
# SteamInstallPath should point to the directory where the corresponding Steam.exe
# resides
#
# To do a debug launch:
#
# - do at least one launch from the UI first to ensure the Minimum Footprint files
# are present
# - leave the Steam UI running
# - copy this file into the App directory
# - fill out the following config parameters
# - run the app directly or through the debugger, with "-steam" on the command line
#
# You may leave it setup and still do normal launches through the
# Steam UI. However, if you comment out the SteamInstallPath parameter,
# you must also REMOVE Steam.dll from the App directory, or else the
# launch will fail with "The local Steam service is not running".
#
SteamAppId=10
SteamAppVersionId=0
SteamInstallPath=C:\Steam
SteamAppUser=account_name
|
change the SteamInstallPath to point your main Steam dir(where is located steam.exe) if there is spaces put it in quotes.
After that make SteamAppUser to point steam user name.
Then start Steam and leave it to run on background, then force the debugger to run the hl.exe in to the \counter-strike\ folder with this command line
hl.exe -steam -game cstrike
else if you debug Dedicated server you must change the paths in to the debugger to point hlds.exe and you must add this command line
hlds.exe -steam -console -game cstrike -maxplayers 20 +map de_dust2
(you can change the map and the maxplayers values)
Set the work dir in to the debugger(if have such option) to point the folder that hl.exe is located. Now start debugging with Code::Blocks option(it must have such option) and all will be fine.