Getting debug out of the builder - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

davidnewcomb
Posts: 19
Joined: Fri Apr 09, 2010 5:04 pm

Getting debug out of the builder

Is there anyway to get debug messages out of the builder.
I've been trying to build a full size app and it doesn't seem to be able to get to the end.
First time it failed because it ran out of space and the second time it failed here:

[ DefaultBuild ]
Building package (en_GB): Y:\01\cheap02-SetupFiles\cheap02.msi
Creating CAB file(s)... done.
Creating MSI database... done.
Inserting CAB file(s) into MSI...

In the morning when I came back in it was still running. When I clicked cancel on the progress indicator, the cpu went through the roof and the whole app hung (including redraws).

Is there any way to get extra debug out of the builder so I can report bugs.
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Getting debug out of the builder

Hi,

I'm afraid you cannot debug the build process.

Can you please send us the aip file that fails to build to support at advancedinstaller dot com so we can investigate it?

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
davidnewcomb
Posts: 19
Joined: Fri Apr 09, 2010 5:04 pm

Re: Getting debug out of the builder

I think the problem is related to where your files are. Our source is under clearcase control and so we often write installers based on network drives.
There are 3 components to the AI set up: temporary storage (%TMP%/%TEMP%), source AI file and objects to install.
The only way I could get it to work was if all the objects were copied on to the c: drive and make sure the temporary files are also on the c: drive.
If the object files were on a remote drive it would hang in the middle.

Now that I know it takes 26 minutes to create my package, I can determine if there was a hang or whether I was being impatient.

Eventually this program will be run from the command line as part of our build process, so I'm a little bit worried that there won't be enough information to determine how the build failed. On the flip side I haven't seem many error messages.

Return to “Common Problems”