question

wills-0518 avatar image
0 Votes"
wills-0518 asked RoyLi-MSFT edited

Address Sanitizer in UWP app?

I'm trying to run the Visual Studio Address Sanitizer with a UWP C++ app. It doesn't seem to be working.

  • First I created a new UWP app with DirectX 12 and called it UWPDX12App.

  • Then I went to the UWPDX12App project properties page and set "Enable Address Sanitizer" to "Yes (/fsanitize=address)" under the C/C++ menu.

When launching the app with the address sanitizer enabled, I get the following dialog boxes:

Unable to activate Windows Store app '0c0...!App'. The UWPDX12App.exe process started, but the activation request failed with error 'The target process aborted before activation completed. More information may be available in the Debug pane of the Output window (Debug->Windows->Output)'.

See help for advice on troubleshooting the issue.

C5lifap.png

Unable to activate Windows Store app '0c0...!App'. The UWPDX12App.exe process started, but the activation request failed with error 'The app didn't start'.

See help for advice on troubleshooting the issue.

GmNc53l.png

In the output window, I see:

The program '[23192] UWPDX12App.exe' has exited with code -1073741515 (0xc0000135) 'A dependent dll was not found'.


not-supported
· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I can't offer you a solution, but I've similarly found trying to use address sanitizer in anything but simple application scenarios was unworkable. While it's not the same as your situation, I wasn't able to get it to work with an Explorer shell extension when I last tried.

1 Vote 1 ·
wills-0518 avatar image wills-0518 DavidLowndes-6766 ·

Why? What was the blocking issue when you tried to run it?

0 Votes 0 ·

It's been several months since I last tried it, but this post notes:

Loading a DLL built –fsanitize=address and running with an EXE not compiled –fsanitize=address is unsupported. Even calling LoadLibary from main would result in false positives.

I persisted for a while but eventually gave up on it as I was only trying AS as it was new to see if it showed anything up - my project is very mature and I wasn't expecting it to find any unknown problems.

If you can supply a small project that reproduces the issue, I guess you could submit a bug report to MS using the VS Report a Problem facility.


1 Vote 1 ·

Since this issue happens even when you tested in a new project. I agree with Davidlowndes that it is suggested you should submit feedback using the VS report.

1 Vote 1 ·

0 Answers