Ticket #32 (new defect)
Investigate problems on Vista, fix them if necessary
| Reported by: | debrouxl | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | Version 1.00 |
| Component: | project | Version: | 0.96 |
| Keywords: | Cc: |
Description
(byproduct of a discussion with lachprog)
(priority higher than normal, because better working tools would be a user-visible advantage of GCC4TI over TIGCC)
TIGCC doesn't work as well on Vista as on older versions of Windows. This was reported multiple times, e.g.
Spaces in user programs' paths (and/or TIGCC path ?) seem to worsen problems.
We have to investigate the extent of the problems:
- get a reproducable testcase. I'm going to ask the two yAronet users who created the aforementioned topics whether they've saved a reproducable testcase;
- find out the list of TIGCC executables which are affected. We know the Delphi IDE is affected, but aren't tprbuilder (written in C) and TIGCC (whose Windows version is currently written in Delphi) affected as well ?
- see whether recompiling the affected executables with a newer compiler / environment (VS 2005 or 2008, Delphi 2009) solves the problem.
(While we're at recompiling the IDE executable: we could solve ticket #15. The VTI support was removed from the Delphi IDE on 20061030, starting at r893)
I have VS 2008 on a rather space-starved Windows XP partition.
Who has Vista ? Who has Delphi 2009 ?
Attachments
Change History
Changed 3 years ago by debrouxl
-
attachment
buggy.tar.bz2
added
comment:1 Changed 3 years ago by debrouxl
Daniel Vouaux, the creator of the second topic, sent me a testcase. He says the behaviour is always reproducable when putting the contents of the tarball in 'Mes Documents\Buggy', when TIGCC is installed in 'C:\Programmes\TIGCC'.
Can somebody please reproduce this behaviour ?
comment:2 Changed 3 years ago by debrouxl
Daniel put the contents of the tarball at C:\Users\Daniel\Desktop\Documents\Buggy, Documents being a folder he created on the desktop.
I installed Vista in a VM, but I couldn't reproduce the problem, even under a non-SP1 Vista, with variations of the path, and even if using plain TIGCC 0.96 Beta 8 (i.e. not the recompiled versions of the IDE and gcc released several months later)...
Will somebody else have better luck ?
comment:3 Changed 3 years ago by debrouxl
I've got another testcase sent by Wilfried Andoh (andoh_wilfried, creator of the first topic). I don't have luck in reproducing the problem either :'(
I've asked both reporters if they could capture process, file and registry activity using SysInternal?'s ProcessMonitor?. They're willing to help. I sent them the following instructions:
- installer ProcessMonitor?, ou la SysInternals? Tools Suite dont il fait partie;
- lancer ProcessMonitor? avant de lancer l'IDE TIGCC;
- appuyer sur Ctrl+L pour mettre des filtres de capture (pour avoir uniquement les processus qui nous intéressent - non seulement on n'a pas à savoir le reste de ce qui peut se passer sur ton PC, mais ça augmente la taille de la capture, aussi ):
- Process name / is / ide.exe / Include
- Process name / is / tigcc.exe / Include
- Process name / is / cc1.exe / Include
- Process name / is / as.exe / Include
- Process name / is / tprbuilder.exe / Include
- quitter ProcessMonitor? pour redémarrer la capture de zéro;
- relancer ProcessMonitor?, qui propose de remettre les filtres de capture actifs lors de la précédente session: les remettre;
- lancer l'IDE TIGCC, et lancer le build qui ne fonctionne pas;
- quitter l'IDE TIGCC;
- sauvegarder la capture avec uniquement les éléments affichés par le filtre actuel, dans le format natif de ProcessMonitor? (PML).
- fournir un moyen de récupérer la capture. Vu la taille prévisible du fichier, je conseille de compresser les données (ça donne d'excellents résultats, bzip2 m'a divisé la taille d'une capture de 19 MB par 10 et 7-Zip par encore plus).
comment:4 Changed 3 years ago by debrouxl
I've just noticed that I forgot to mention that at http://www.yaronet.com/posts.php?sl=&s=117730&p=1&h=13#13 , I uploaded three ProcessMonitor? traces, in the most expressive available format (ProcessMonitor?'s native format):
- Daniel's machine with UAC enabled (buggy);
- Daniel's machine with UAC disabled (OK);
- my machine with UAC enabled (OK).

Testcase for the behaviour under Vista