-
Notifications
You must be signed in to change notification settings - Fork 264
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
Fetching ntdll symbols for syscall auto-generation failing #2232
Comments
1903 is supported. This is a failure to load symbols which is how DrMemory now supports the frequent Win10 major version updates. Does your machine not have outside network access? Please run with |
My internet is working fine on this machine, I'm not sure why it can't download the symbols. Running with
I left it for a few minutes, but maybe it's just a big download. I'll try again and leave it overnight (my internet is pretty fast here though, so it shouldn't be a download speed problem). I'll look into getting the symbols manually. |
Hi, is there any progress about the issue? I'm facing the same problem, for version 2301 |
I can't reproduce this and it's not clear what is causing the problem. If you could walk through in the debugger as discussed below: The symbols are downloaded from the Microsoft symbol server with this code: https://github.com/DynamoRIO/drmemory/blob/master/drsyscall/pdb2sysfile.cpp#L482 https://github.com/DynamoRIO/dynamorio/blob/master/libutil/dr_frontend_win.c#L505 The error without
Error code 1 is unfortunately the vague I would suggest walking through that code in a debugger to see where it fails and to look at the Windows GetLastError. frontend.c for |
Hey, dude, I'm facing the same problem too. Here's the log:
with -vvv,:
|
That's a different error from what the poster of the issue is hitting:
Is there no network access on that machine? Does symbol loading work with the separate MS tools? E.g., something like this, depending on where you have symchk.exe:
|
I think there are two problems here, first dr. memory needs to be put on the firewall whitelist, so it can download the symbols. The second problem is the crash. There seems to be no solution to that |
The exit code |
If you allow it to download the symbols, then that error goes away, but you then have a different error not related to missing symbols: Dr. Memory version 2.3.0 Application c:\backup\warlord\Warlord\debug\MercTactics.exe (11796). Dr. Memory internal crash at PC 0x6f86d99b. Please report this at http://drmemory.org/issues along with the results of running '-debug -dr_debug'. Program aborted. |
Please file a separate issue rather than lumping into this one which is about symbols. Please fill out the bug template for that new issue (supposed to show up on any new bug but a Github bug prevents it if you're not logged in when you click the button) by using this link: https://github.com/DynamoRIO/drmemory/issues/new?assignees=&labels=&template=bug_report.md&title= |
I can confirm that issue is present on the newest DrMemory & Win10. Luckly you can ignore it with "ignore_kernel" DrMemory - 2.3.18696
This issue has tag "Status-NeedInfo" - let me know how could I provide additional info that can be usefull? |
We have not been able to reproduce any of these symbol loading failures. As you can see above (#2232 (comment), ,#2232 (comment)) I suggested several routes to help figure out what is going on: walking through in the debugger; seeing whether symchk by itself works. Is it a firewall or other local network issue specific to your setup that is stopping symbol downloading? |
Even with the firewall disabled, I can't download symbols. I'll try to check other things you mentioned in some free time. |
|
I have some more information about this issue: System: Console with -vvv (when starting as service): |
Im hitting this issue. I tried to run: I then get an HTTP to HTTPs redirect error:
Changing it to https makes it work just fine The Drmemory log seems to indicate that it's pointed at the http url: |
Similar to #2126, I think, but for a different version (1903).
When running Dr Memory, I get the following output:
The text was updated successfully, but these errors were encountered: