Edit - Stack Overflow

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

"Easy to use" is subjective. With a GCC extended assembly block, all we get is a line number pointing to the end of the block (the closing paren), and not the actual variable causing the problem. That's even with --track-origins.

jww
– jww

2015-08-17 15:54:09 +00:00
Commented Aug 17, 2015 at 15:54
@jww this is a gcc problem (not producing enough debug info), not a valgrind problem. It might go away if you compile your source with -ggdb or something, but I'd be surprised. I'm working in llvm backends and its much the same situation there.

Will
– Will

2015-08-18 05:20:55 +00:00
Commented Aug 18, 2015 at 5:20
It seems that purify is no longer a a good option: marlowa.blogspot.com.br/2015/08/the-death-of-purify.html

VinGarcia
– VinGarcia

2018-01-30 01:13:36 +00:00
Commented Jan 30, 2018 at 1:13

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »

Collectives™ on Stack Overflow