Skip to content
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

[error] Uh oh! Mull corrupted LLVM module. #993

Closed
RobertoBagnara opened this issue Apr 2, 2022 · 6 comments
Closed

[error] Uh oh! Mull corrupted LLVM module. #993

RobertoBagnara opened this issue Apr 2, 2022 · 6 comments

Comments

@RobertoBagnara
Copy link

We just upgraded Mull from a very old version.
We are now using https://github.com/mull-project/mull/releases/download/0.17.1/Mull-12-0.17.1-LLVM-12.0-ubuntu-20.04.deb
Following the tutorials, I think we managed to revise all our scripting in the correct way, but now we stumble upon a bungh of errors of the form

[error] Uh oh! Mull corrupted LLVM module.
Please, report the following error message here https://github.com/mull-project/mull/issues
Underlying error message:
Invalid indices for GEP pointer type!
  %7 = getelementptr inbounds %struct.m_uint8_t, %struct.m_uint8_t* %6, i32 0, i32 42, !dbg !226
...

The attached typescript contains several occurrences:

LOG.txt

@AlexDenisov
Copy link
Member

Hi @RobertoBagnara, could you also share the config file (mull.yml)?

@RobertoBagnara
Copy link
Author

RobertoBagnara commented Apr 20, 2022

Sure, it is very short:

mutators:
 - all

timeout: 10000

quiet: false

@AlexDenisov
Copy link
Member

I'd suggest sticking to cxx_all as all includes experimental mutators some of which are currently broken.
@RobertoBagnara could you give it a try?

@RobertoBagnara
Copy link
Author

RobertoBagnara commented Apr 21, 2022

It seems to work now, with "cxx_all" instead of "all": thanks!

@AlexDenisov
Copy link
Member

The all is not supposed to be used by end users, I'll add a warning when it happens to avoid confusion.
Thank you so much for bringing this up @RobertoBagnara!

@AlexDenisov
Copy link
Member

I extended diagnostics to handle such cases here #1000.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants