-
Notifications
You must be signed in to change notification settings - Fork 13.5k
[MC] SIGSEGV due to nullptr AsmParser.Out.CurrFrag #97635
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
Comments
@MaskRay Could you kindly comment if this failure makes sense? |
Hi @sivan-shani, do you have a reproduce? Are you a library user for a downstream project? The upstream testsuite is asan and msan clean.
|
Thank you for the reply. The jist of it is the usage of I will follow the gdb run again to double check,but I do believe that |
Interesting!
The Perhaps your internal tool does something that adds an element to
|
Apologizes, I was wrong. The execution does hit |
If there is a
|
It seems as Will try and create a reproducer tomorrow. Meanwhile perhaps this data might be insightful:
|
Hello, apparently the |
Not an issue - happen due to an external re-implementation of the |
Due to several recent changes, the function
AsmParser::checkForValidSection()
is now utilizing (among other functions) alsoCurFrag->getParent()
instead ofgetCurrentSection().first
This seems to cause a SIGSEV in some cases when
AsmParser::Run()
is called via API.AsmParser.Out.CurFrag
is Edit: set to nullptr,AsmParser::Run()
-> call ->AsmParser::parseStatement
->checkForValidSection
Edit: which callCurFrag->getParent()
and this terminates in SIGSEV.gdb output:
The text was updated successfully, but these errors were encountered: