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

Investigate segfaults due to wrong API usage. #406

Open
edg-l opened this issue Jan 18, 2024 · 1 comment
Open

Investigate segfaults due to wrong API usage. #406

edg-l opened this issue Jan 18, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@edg-l
Copy link
Contributor

edg-l commented Jan 18, 2024

Sometimes using the api the wrong way, like passing a the wrong type to memref, or other dialects can cause a segfault (i think specially with the pass manager and sometimes verify(?)).

I'll try to have minimal examples when i can, but just wanted to mention i noticed segfaults during my development using melior.

@raviqqe raviqqe added the bug Something isn't working label Feb 16, 2024
@raviqqe
Copy link
Owner

raviqqe commented Mar 14, 2024

Calling mlirLLVM*TypeGet functions without loading the LLVM dialect results in SEGV.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants