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 data is missing in fxn dictionary #11

Open
saloid opened this issue Jan 26, 2021 · 2 comments
Open

Error data is missing in fxn dictionary #11

saloid opened this issue Jan 26, 2021 · 2 comments

Comments

@saloid
Copy link

saloid commented Jan 26, 2021

Getting this errors.

Error data is missing in fxn dictionary {'tu': '.\\flexcan_irq.c', 'name': 'CAN0_ORed_IRQHandler.localalias.0', 'binding': 'LOCAL'}
Error data is missing in fxn dictionary {'tu': '.\\flexcan_irq.c', 'name': 'CAN1_ORed_IRQHandler.localalias.1', 'binding': 'LOCAL'}
Error data is missing in fxn dictionary {'tu': '.\\flexcan_irq.c', 'name': 'CAN2_ORed_IRQHandler.localalias.2', 'binding': 'LOCAL'}
Traceback (most recent call last):
  File "../../toolchain/WCS/WCS.py", line 431, in <module>
    main()
  File "../../toolchain/WCS/WCS.py", line 422, in main
    resolve_all_calls(call_graph)
  File "../../toolchain/WCS/WCS.py", line 243, in resolve_all_calls
    resolve_calls(fxn_dict)
  File "../../toolchain/WCS/WCS.py", line 229, in resolve_calls
    for call in fxn_dict2['calls']:
KeyError: 'calls'

Not sure what it mean, but here how this functions looks in code:

void CAN2_ORed_IRQHandler(void)
{
    FLEXCAN_IRQHandler(2U);
}

This code is from NXP SDK for S32K144 MCU.

@saloid
Copy link
Author

saloid commented Jan 26, 2021

It's interrupt handlers, so they are never called from code, Maybe it's an issue. Anyway, is it possible to ignore such functions?

@DEvil0000
Copy link

DEvil0000 commented Aug 29, 2022

This is a tricky one to come up with a good fix but I suggest to set data['calls'] = set() as a quick fix to get some result at all.
for a better fix: functions without caller may get called by a function pointer or other methods so for a worst case scenario they should be considdered called on top of the worst call.

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