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

cling error recovery issues #7970

Open
Axel-Naumann opened this issue Apr 22, 2021 · 5 comments
Open

cling error recovery issues #7970

Axel-Naumann opened this issue Apr 22, 2021 · 5 comments
Assignees

Comments

@Axel-Naumann
Copy link
Member

Describe the bug

root [1] .rawInput
root [2] std::vector<short> getV() { return {42}; }
root [3] .rawInput
root [4] getV()[0].foo()

and that last line shows an error, good! But now:

root [5] getV()[0]
IncrementalExecutor::executeFunction: symbol '_ZSt8_DestroyIPssEvT_S1_RSaIT0_E' unresolved while linking [cling interface function]!
You are probably missing the definition of void std::_Destroy<short*, short>(short*, short*, std::allocator<short>&)
Maybe you need to load the corresponding shared library?

Expected behavior

To Reproduce

Setup

Additional context

@github-actions github-actions bot added this to Needs triage in Triage Apr 22, 2021
@jalopezg-git
Copy link
Collaborator

Thanks for the report, @Axel-Naumann! We already have several issues with seemingly the same origin (removing symbols from the JIT that are not re-emitted, apparently because they came from a PCH/module).

I was taking a look into this last week, but still don't have a fix for it. I will continue working on it. :-)

@Axel-Naumann
Copy link
Member Author

Axel-Naumann commented Apr 22, 2021

Those I know of - but here the specialization is not coming from the PCH/PCM. (You can try to MyClass if you don't believe me ;-) ) And: thanks for looking at it!

@hahnjo
Copy link
Member

hahnjo commented Dec 13, 2023

Still fails for me in master - probably because of my last commit to make the tests pass on macOS 😐

@hahnjo hahnjo reopened this Dec 13, 2023
@dpiparo
Copy link
Member

dpiparo commented Feb 3, 2024

I cannot reproduce on (mac, linux)x(6.30.04,master). I close the issue, please do not hesitate to re-open if I am missing something (@hahnjo @devajithvs)

@dpiparo dpiparo closed this as completed Feb 3, 2024
@dpiparo dpiparo added this to Issues in Fixed in 6.30.06 via automation Feb 3, 2024
@hahnjo
Copy link
Member

hahnjo commented Feb 5, 2024

I still get exactly the error described in the summary with master:

   ----------------------------------------------------------------------------
  | Welcome to ROOT 6.31/01                                  https://root.cern |
  | (c) 1995-2024, The ROOT Team; conception: R. Brun, F. Rademakers           |
  | Built for linuxx8664gcc on Feb 05 2024, 07:24:23                           |
  | From heads/ntuple-RPageNullSink@v6-31-01-913-gfdecca9b4d                   |
  | With clang version 16.0.6 (Red Hat 16.0.6-2.module_el8.9.0+3621+df7f7146)  |
  | Try '.help'/'.?', '.demo', '.license', '.credits', '.quit'/'.q'            |
   ----------------------------------------------------------------------------

root [0] .rawInput
Using raw input
root [1] std::vector<short> getV() { return {42}; }
root [2] .rawInput
Not using raw input
root [3] getV()[0].foo()
ROOT_prompt_3:1:10: error: member reference base type 'value_type' (aka 'short') is not a structure or union
getV()[0].foo()
~~~~~~~~~^~~~
root [4] getV()[0]
IncrementalExecutor::executeFunction: symbol '_ZSt8_DestroyIPssEvT_S1_RSaIT0_E' unresolved while linking [cling interface function]!
You are probably missing the definition of void std::_Destroy<short*, short>(short*, short*, std::allocator<short>&)
Maybe you need to load the corresponding shared library?

@hahnjo hahnjo reopened this Feb 5, 2024
@hahnjo hahnjo removed this from Issues in Fixed in 6.30.06 Feb 8, 2024
@dpiparo dpiparo assigned dpiparo and unassigned Axel-Naumann Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants