You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It calls linking. The error reporting of linking calls from_type which uses the mode of the symbol: linkingt::copy_symbols linkingt::duplicate_non_type_symbol linkingt::duplicate_code_symbol linkingt::detailed_conflict_report linkingt::detailed_conflict_report_rec linkingt::type_to_string_verbose from_type
At the moment having the mode as anything other than "json_symtab" will result in an invariant failure.
While its not the biggest problem in the world, it does seem that adding more 'language modes' to json_symtab_language makes it an increasing maintenance burden over time (e.g. harder to add sensible invariants, easier for language specific implementation details to leak into dark corners of code, etc). I think I prefer the proposals in #6219 personally (see comments I'm about to add there...)
I don't yet have a reproducer for this issue but it seems that there is a design / architectural problem.
symtab2gb
only loads thejson_symtab
language:cbmc/src/symtab2gb/symtab2gb_parse_options.cpp
Line 115 in 665abf7
It calls linking. The error reporting of linking calls
from_type
which uses the mode of the symbol:linkingt::copy_symbols
linkingt::duplicate_non_type_symbol
linkingt::duplicate_code_symbol
linkingt::detailed_conflict_report
linkingt::detailed_conflict_report_rec
linkingt::type_to_string_verbose
from_type
At the moment having the mode as anything other than
"json_symtab"
will result in an invariant failure.So, potential work-arounds or solutions:
"json_symtab"
( paging @danielsn for the connection to RFC: Language mode for Rust #6219 ).symtab2gb
and set the mode toID_C
(as it is at the moment).( See also #6219 (comment) )
The text was updated successfully, but these errors were encountered: