-
Notifications
You must be signed in to change notification settings - Fork 860
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
valgrind doesn't work #120
Comments
It might be helpful to collect a strace to see which syscall is failing? Or you can take it a step further by comparing it to a strace from a real Ubuntu box. |
I have been getting the same bug as @tycho. I collected a strace and here's the full strace output:
|
My bet is the |
None of the following memory tools are working atm:
|
Tried with clang as well and no luck
Strace
|
problem still present on build 14328 |
Also getting this exact error on 14332 |
Also having this issue on build14342 strace
Let me know if there is anything else you want me to test out or run. edit: Changed Stack Trace to strace because stack trace was wrong, lol. Thank you @tycho |
@jbhum nitpick: that's not a stack trace, it's an strace, or syscall trace. |
Issue still there with 14366. |
Ok so it looks like I'm not the only one with the problem, having this issue on 14372. Are there any work around? I have been needing to scp onto a linux machine to use valgrind. |
Just re-tested on 14385, and valgrind still does not run. I don't know of any workaround. I guess we will have to wait for after RS1? |
Hi for me it helped to download sources and compile (./configure, make, make install , make clean , make distclean) in bash. valgrind installed from repositories writed above rubbish. |
Installing Valgrind 3.11.0 from source also works for me (currently on Windows Anniversary build). Thanks @povijarrro . |
If you find the delta in config.log between a native Linux machine and a On Aug 10, 2016 7:59 PM, "MotorizedWandOfFury" notifications@github.com
|
I have also installed Valgrind 3.11.0 from source (on Windows 10 14393.82 version 1607). It seems to work well. Thanks to @povijarrro and @MotorizedWandOfFury. |
Have you guys managed to make callgrind work ? It seems i have a seg fault with it. |
I had segmentation fault problems with callgrind using callgrind_control and malloc. I don't actually use this tool, I often use memcheck. |
= sync = Little changes = Started reprocessing DEVEL source code = Added valgrind exec support in Makefile (Untested on BashOnWindows: microsoft/WSL#120)
Installing from repository solved the first issue, but now I am getting the General protection fault as you guys... Any fixes for that?
|
@byvlstr As per my comment in #1295 I have a dirty hack that at least gets you past the SIGSEGV: https://github.com/Grauniad/valgrind It's not perfect - but applying this change to the 3.12.0 release of valgrind gets you going at least. Note that:
...so use it at your own risk :) @arthurpham: The callgrind suite passes clean on my machine, but 1 & 2 still apply... |
@Grauniad Outstanding investigation, thank you very much! Fix is checked in. |
Is it expected that I still got this behavior? I kept my Windows 10 and Ubuntu updated. Is this released? |
Thanks @povijarrro that worked! |
This issue was previously closed, but I'm not sure what the outcome was. Is valgrind supposed to work directly off apt, or is it only supposed to work if installing from source? I got version 3.10.1-1 off apt (Windows version 1703), and received the original error message (aspacem assertion failed). |
I found that using this method solved it for me, however it could have been a coincidence/my code was just too simple, but every test I did that involved intentional memory leaks were properly tracked (I have no attachment to my current LSFW install as I haven't been able to do anything noteworthy in it yet, so I just nuked the whole install and reinstalled it (which is a very quick process btw)) lxrun /uninstall To uninstall and trash/home directory on WSL: lxrun /uninstall /full To install again: lxrun /install To install again without user & password (always root): lxrun /install /y |
I'm currently on Windows 10 Pro (Version 10.0.15063 Build 15063) and I had no trouble at all installing and using Valgrind. |
@Kyrluckechuck Thanks, I didn't realise I needed to reinstall. |
Valgrind works after I installed Windows 10 creator update (version 1703) and reinstalled Bash/WSL :) |
Actually the workaround works well till a few days ago...
Not sure why, but finally I realize this is in my |
@FranklinYu No. I was using alwsl but this time it was based on a squashfs'd backup of my previous installation. (So I had a hard time to remove my |
The text was updated successfully, but these errors were encountered: