Burn: cmd property value with escaped quots breaks engine #3890

Closed
wixbot opened this Issue Jan 15, 2013 · 6 comments

Comments

Projects
None yet
2 participants
@wixbot
Collaborator

wixbot commented Jan 15, 2013

Engine acts very weird if it accepts escaped double quots in value of some property from cmd launch:
SomeBundle.exe SOMEPROPERTY="Some""Value"
It creates billion SomeBundle.exe processes which do nothing.

Originally opened by vadok86 from http://sourceforge.net/p/wix/bugs/3190/

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot Jun 5, 2013

Collaborator

The same symptom occurs with a backslash followed by quotes, for example:

Setup.exe TargetDir="c:\some path"

Collaborator

wixbot commented Jun 5, 2013

The same symptom occurs with a backslash followed by quotes, for example:

Setup.exe TargetDir="c:\some path"

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot Oct 10, 2013

Collaborator

Originally changed by barnson
Area changed from cmd property value escaped quots bundle to burn
Release changed from v3.8 to v3.x

Collaborator

wixbot commented Oct 10, 2013

Originally changed by barnson
Area changed from cmd property value escaped quots bundle to burn
Release changed from v3.8 to v3.x

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot Apr 25, 2014

Collaborator

Hello,

we have encoutered same behaviour. Finally we found that source of the problem is unicode character used in parameter on command line. In our case it was quote mark ' ” ' with 0x e2 80 9d.

Once it was used in command line, burn engine had started around child 300 instances and then crashed with error :
[1E28:0B18][2014-04-17T16:47:58]e000: Error 0x800705b4: Failed to open parent pipe: .\pipe\BurnPipe.{BECF5A3E-6E28-4F77-BB18-7E2207686CB5}
[1E28:0B18][2014-04-17T16:47:58]e000: Error 0x800705b4: Failed to connect to unelevated process.
[1E28:0B18][2014-04-17T16:47:58]e000: Error 0x800705b4: Failed to run per-machine mode.

Please can you fix this issue somehow?

Thank you in advance

OnMi

Originally posted by onmi

Collaborator

wixbot commented Apr 25, 2014

Hello,

we have encoutered same behaviour. Finally we found that source of the problem is unicode character used in parameter on command line. In our case it was quote mark ' ” ' with 0x e2 80 9d.

Once it was used in command line, burn engine had started around child 300 instances and then crashed with error :
[1E28:0B18][2014-04-17T16:47:58]e000: Error 0x800705b4: Failed to open parent pipe: .\pipe\BurnPipe.{BECF5A3E-6E28-4F77-BB18-7E2207686CB5}
[1E28:0B18][2014-04-17T16:47:58]e000: Error 0x800705b4: Failed to connect to unelevated process.
[1E28:0B18][2014-04-17T16:47:58]e000: Error 0x800705b4: Failed to run per-machine mode.

Please can you fix this issue somehow?

Thank you in advance

OnMi

Originally posted by onmi

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot May 29, 2014

Collaborator

Originally changed by rseanhall
AssignedTo set to shall

Collaborator

wixbot commented May 29, 2014

Originally changed by rseanhall
AssignedTo set to shall

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot May 29, 2014

Collaborator

Pull request - wixtoolset/wix3#51

Originally posted by rseanhall
Release changed from v3.x to v3.9

Collaborator

wixbot commented May 29, 2014

Pull request - wixtoolset/wix3#51

Originally posted by rseanhall
Release changed from v3.x to v3.9

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot Jun 2, 2014

Collaborator

Pull request merged.

Originally posted by rseanhall
Resolution set to fixed
Status changed from Open to Resolved

Collaborator

wixbot commented Jun 2, 2014

Pull request merged.

Originally posted by rseanhall
Resolution set to fixed
Status changed from Open to Resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment