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

undefined function elixir_erl:debug_info/4 #59

Open
rlipscombe opened this issue Aug 12, 2020 · 3 comments
Open

undefined function elixir_erl:debug_info/4 #59

rlipscombe opened this issue Aug 12, 2020 · 3 comments

Comments

@rlipscombe
Copy link
Contributor

Googling for the above error gets me to josefs/Gradualizer#73 (comment), which suggests that I "didn't link in the Elixir library location".

This makes some kind of sense: I'm compiling a mixed Erlang/Elixir project, and covertool is dying on the Elixir part with the above error. How do I tell covertool about the "Elixir library location"?

@rlipscombe
Copy link
Contributor Author

I worked around it with the following:

ERL_LIBS=$(elixir --eval 'IO.puts(Path.dirname(Path.dirname(:code.which(:elixir_erl))))') covertool ...

@nalundgaard
Copy link
Member

Not sure what the right patch for this would be—is there a way to detect that once you've started covertool? seems like no. Maybe we should just add a README section on putting that snippet in a make target in your mixed Erlang/Elixir projects?

@rlipscombe
Copy link
Contributor Author

rlipscombe commented Aug 14, 2020

Not sure what the right patch for this would be

Me neither.

is there a way to detect that once you've started covertool?

I can't think of a clean way, no. And even if you could, how would covertool know where the Elixir libs are? Is there a way to detect that it's an Elixir module and to skip it? Not sure, and I'm not sure that's the correct answer -- I haven't proved that this happens with all Elixir modules.

Maybe we should just add a README section

Seems like the best option.

Alternatively, I was kinda thinking that just by having this issue here, Google would find it for the next person.

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