QualityCentral

Public Report

Report From: Delphi-BCB/IDE/Dialogs [ Add a report in this area ]

Report #: 90436

Status: Closed

Using the '$' character in path names causes loop in IDE

Project: Delphi

Build #: 15.0.3953.35171

Version: 15.1

Submitted By: Richard Walton

Report Type: Crash / Data loss / Total failure

Date Reported: 12/20/2010 5:02:35 PM

Severity: Serious / Highly visible problem

Last Updated: 9/5/2012 8:13:27 PM

Platform: All versions

Internal Tracking #: 281486

Resolution: Fixed (Resolution Comments)

Resolved in Build: : 17.0.4625.53395

Duplicate of: None

Voting and Rating

Overall Rating: No Ratings Yet

0.00 out of 5

Total Votes: 10

Description

Adding a library path containing both an environment variable and a directory containg the '$' character causes the IDE to enter an infinite loop. Right clicking the Delphi XE icon on the taskbar and clicking Close shuts it down.

Restarting Delphi shows that the directory has not been added to the library path list.

As well as library paths, the JCL component set adds a directory to the Debug DCU path list. If this directory contains the '$' character then pressing F9 to run a Delphi project causes the IDE to enter a CPU loop.

This is a major problem because our directory structure includes folders prefixed with the '$' character.

Steps to Reproduce:

The problem can be reproduced as follows:

1. Create a '$stuff' directory in the projects directory.
2. In the IDE go to Tools->Options->Library->Library path.
Or, go to Project->Options->Delphi Compiler->Serach path.
3. Try to add a library called $(BDSPROJECTSDIR)\$stuff.

At this point bds.exe will go into a CPU loop. Right clicking the Delphi icon in the taskbar and clicking Close will shut down the IDE.

Restarting Delphi shows that the directory has not been added to the library path list.

Workarounds

None

Attachment

None

Comments

Richard Walton at 10/13/2011 2:52:32 PM -

It's been a while since reporting this issue and no fix appears to have been released. Any idea when one may be forth coming?

Tomohiro Takahashi at 10/13/2011 6:10:31 PM -

Unfortunately, this issue is still Open.
so, as you know, QC is not technical support service. If you need official reply from Embarcadero, please contact technical support. Sorry for inconvenience.
http://support.embarcadero.com/

Richard Walton at 10/13/2011 8:23:34 PM -

Thanks for your reply.

I thought QC was the way to report problems to technical support.

Nevertheless the fact that this QC entry has been OPENed and has an internal tracking number implies that technical support must at least be aware of it.

It's a bit surprising that a report marked as "Crash/Data loss/Total failure" with severity "Serious/Highly visible" hasn't been fixed in the 10 or so months since it was reported regardless of how many users are affected.

Developer Tools

Database Tools