Debugging Installations

Black_End · 31st July 2002, 17:19

Hi,
I would like to add some features to NSIS and in order to-do that I need to debug the Installation the actual exehead. Does someone found a way todo so?

-BlackEnd

kichik · 31st July 2002, 17:32

Debug version of NSIS never compiled right. You have two options, first is to make the debug version compile, second is to just use message boxes.

Black_End · 1st August 2002, 07:24

What's the Debug Version The Project compiled in Debug Mode? it compiles well for me. I think that the best way to debug will be warp all exehead in a DLL, so that the Installation will only load the dll and pass the data to it. That way it will be easy to debug the actual installation. Has some one done it?, how the hell Justin debug it?

kichik · 1st August 2002, 07:26

By debug version I mean that the project is compiled in debug mode, yes.

Personally, I just use MessageBoxes... No need for fancy shmensy debuging tools. I have no idea how Justin does it.

Sunjammer · 1st August 2002, 07:36

You could use the OutputDebugString command and capture the output using the DebugView tool.

Black_End · 1st August 2002, 07:39

MessageBox, OutputDebugString, I'm going to implement the DLL debugging. Not having the ability to proper debug the installation engine will not get it too far...

Sunjammer · 1st August 2002, 07:41

However remember that OutputDebugString has many advantages in some situations over actually using the debugger. It doesn't screw up timing, threads still run while you see what's going on, and many others. All I'm saying is don't dismiss OutputDebugString so easily

Black_End · 1st August 2002, 08:52

OutputDebugString does a context switch, those "Screwing" your thread timing...

Sunjammer · 1st August 2002, 08:56

Sorry I was meaning large scale (i.e. human terms like seconds) level timing is screwed by halting in a debugger when u can just watch OutputDebugString info, and secondly the only way I can see what is going on with multiple threads of execution running (that aren't highly sensitive to small timing issues like a context switch) is using logged output rather than a debugger.

Anyway nuff said, it was just a suggestion

31st July 2002, 17:19	#1
Black_End Junior Member Join Date: Jul 2002 Posts: 4	Debugging Installations Hi, I would like to add some features to NSIS and in order to-do that I need to debug the Installation the actual exehead. Does someone found a way todo so? -BlackEnd

31st July 2002, 17:32	#2
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	Debug version of NSIS never compiled right. You have two options, first is to make the debug version compile, second is to just use message boxes. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

1st August 2002, 07:26	#4
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	By debug version I mean that the project is compiled in debug mode, yes. Personally, I just use MessageBoxes... No need for fancy shmensy debuging tools. I have no idea how Justin does it. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

1st August 2002, 07:24	#3
Black_End Junior Member Join Date: Jul 2002 Posts: 4	What's the Debug Version The Project compiled in Debug Mode? it compiles well for me. I think that the best way to debug will be warp all exehead in a DLL, so that the Installation will only load the dll and pass the data to it. That way it will be easy to debug the actual installation. Has some one done it?, how the hell Justin debug it?

1st August 2002, 07:36	#5
Sunjammer Major Dude Join Date: Jun 2002 Location: Swindon, UK Posts: 559	You could use the OutputDebugString command and capture the output using the DebugView tool.

1st August 2002, 07:39	#6
Black_End Junior Member Join Date: Jul 2002 Posts: 4	MessageBox, OutputDebugString, I'm going to implement the DLL debugging. Not having the ability to proper debug the installation engine will not get it too far...

1st August 2002, 07:41	#7
Sunjammer Major Dude Join Date: Jun 2002 Location: Swindon, UK Posts: 559	However remember that OutputDebugString has many advantages in some situations over actually using the debugger. It doesn't screw up timing, threads still run while you see what's going on, and many others. All I'm saying is don't dismiss OutputDebugString so easily

1st August 2002, 08:52	#8
Black_End Junior Member Join Date: Jul 2002 Posts: 4	OutputDebugString does a context switch, those "Screwing" your thread timing...

1st August 2002, 08:56	#9
Sunjammer Major Dude Join Date: Jun 2002 Location: Swindon, UK Posts: 559	Sorry I was meaning large scale (i.e. human terms like seconds) level timing is screwed by halting in a debugger when u can just watch OutputDebugString info, and secondly the only way I can see what is going on with multiple threads of execution running (that aren't highly sensitive to small timing issues like a context switch) is using logged output rather than a debugger. Anyway nuff said, it was just a suggestion