Talk:Code sanitizer

The heap buffer overflow example output is incorrect

Looks like a copy-paste of the heap-use-after-free example above. Can someone fix this example with the appropriate asan output for the buffer overflow example? — Preceding unsigned comment added by 2620:0:1000:1B03:E4A4:17C:5B9E:F25C (talk) 23:58, 8 January 2015 (UTC)
I fixed the compile command and fixed the output. However I can't figure out how to cut and paste and keep the output colors... --Skintigh (talk) 16:09, 20 May 2016 (UTC)

What does it mean "to slow down sth. by n times"?

The article says "The tool slows down programs by approximately 2 times ." and I do not understand what is meant. The question that comes to mind is: Compared to what other slowdown is it two times slower? Even if it is rewritten to "The tool slows down programs approximately by a factor of two." I find the meaning not very easy to grasp and am still unsure about it.

After some thinking I think the author means: "The modified program takes twice the time of the original program to complete." or "It has half the speed compared to the original."

I took a quick look at the source material to verify my assumption and I have to say, that without Figure 2, I had problems knowing what the authors of the paper meant by a "73 % slowdown". What does that mean:

1. Is the speed only 27 % of the original program.
2. Does it take 73 % more time to complete?

With the graph in figure 2 it is clear that what is actually meant is: The time it takes to complete is increased by 73 % on average. I think the ambguity of the paper is kind of transferred to this article.

I am no native speaker of the English language, so I might not know this particular way of expression, correct me if I am wrong.

217.227.17.62 (talk) 17:07, 6 October 2014 (UTC)

If you use the address sanitizer (in gcc this can be done with the parameter -fsanitize=address) then you also have to add -lasan to your linker options. This means, your binary, that gets build, gets this asan stuff included and this is, what slows your binary down compared to a binary without this option enabled. Thus from my understanding it is a good thing to use this feature only for none release builds. If I'm wrong, please feel free to correct me. If my information is correct, then it would make sense to mention in the article that this is actually only intended for development and not for retail builds. 84.158.120.82 (talk) 15:16, 7 August 2024 (UTC)

why %t in the example commands?

Why %t in commands like clang++ -O -g -fsanitize=address %t && ./a.out? Is this defined by AddressSanitizer, by clang, or by the shell? If the latter, then we need to specify which shell. — Preceding unsigned comment added by Quintus V. (talk • contribs) 09:05, 9 February 2020 (UTC)

The comment looks like a unittest thing, where %t is the test file name. Let's clarify it. Artoria2e5 🌉 02:08, 2 March 2023 (UTC)

ReactOS may eventually port and use this

https://reactos.org/project-news/victor-perevertkin-hired-full-time/ — Preceding unsigned comment added by 68.67.254.133 (talk) 19:10, 18 July 2020 (UTC)