-
Notifications
You must be signed in to change notification settings - Fork 10
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
SymInitialize gets broken search paths #5
Comments
Do you have any more info on what SymInitialize() requires for its paths? |
Another question... I'm not really sure how I would handle something like this. If I get the path '../whoppa' I need to first get the absolute path. But if the application has changed cwd() I'm not really sure where the '..' is from? |
Hmm, I see I've left out some vital information on how to reproduce the issue. Great. Because now I don't remember :) I believe that in our case, we launched the application with '..' in the path, i.e. in a command prompt, launch an exe with:
Which would result in a path inside the program which would be |
I have tried a lot of cases here on the machine I have access to and I can only get GetModulePath() to return absolute-paths... But I guess this might be some version problem or similar. |
I also did a test to just hard code paths with dots all over the place and I still worked so that might be due to the version of dbghelp.dll that is loaded? |
It seems that
mod = GetModuleFileName((HMODULE)0, search_path, length);
instatic void callstack_symbols_build_search_path(char* search_path, int length)
can return a path with '..' in it. SymInitialize doesn't play well with this, so the path needs to be sanitized prior to usageThe text was updated successfully, but these errors were encountered: