-
Notifications
You must be signed in to change notification settings - Fork 75
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 when using c_node #516
Comments
If this issue happens, there is probably something wrong with how you start the dataflow or the environment variables that are being passed to your process. It seems to be fine in our CI. Would you mind trying what the difference is between the CI and your node, in this very specific context? |
Yes, I tried to run some C examples according to CI, and found that sometimes it does not have the above error, but sometimes it will have the error that |
Could you share a link to your code? It's a bit unclear to me how a segfault could occur inside the |
I just tried this https://github.com/dora-rs/autoware.universe/tree/feature/autoware_dora/tools/C_node_test and c++-dataflow in dora's example. Regarding segfault, I felt during debugging that |
Thanks for the update! So the problem appears to be fixed after updating to |
When my dora version is 0.3.4, it sometimes has this problem. The repo branch of the c library I use is the main branch. When I switch to tags/v0.3.3, the problem does not occur. |
I met same issue after I upgraded to 0.3.4 last night |
I tried to reproduce this a few times with the |
Yes, it only appears sometimes, can you tell me your system information and dora version, and which branch of the dora repo is it (I don't know if this has anything to do with dora-node-api.h or something) |
Describe the bug
I tried to send and receive messages using the C API in dora, but it gave some errors. I found that the init_dora_context_from_env or dora_next_event function had a problem, and then I found that DORA_NODE_CONFIG was not set. I don't know how dora sets DORA_NODE_CONFIG according to the yml file during operation, but this problem did not occur in the 0.3.2 version of dora.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots or Video
![image](https://private-user-images.githubusercontent.com/62335818/334303362-55b5274a-6d54-4000-b8af-6f47a7bb9d1b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ0NDQ1MTQsIm5iZiI6MTcyNDQ0NDIxNCwicGF0aCI6Ii82MjMzNTgxOC8zMzQzMDMzNjItNTViNTI3NGEtNmQ1NC00MDAwLWI4YWYtNmY0N2E3YmI5ZDFiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODIzVDIwMTY1NFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTIxYjllZDRkYjMzMWM4ZDBjYmJlYzM3NTI1OGM4ODQ4NDMwZDAxYTU0YmMyOTE4YTk2ODAyNjQ3ZGY0ZWJhYTImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.uj5eWsS6Ez7lr-mcdTNpNZ3RIXCbaW_k1UktHWWphWQ)
![image](https://private-user-images.githubusercontent.com/62335818/334303600-76a73f2a-685d-463a-b881-1c9a98ddd815.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ0NDQ1MTQsIm5iZiI6MTcyNDQ0NDIxNCwicGF0aCI6Ii82MjMzNTgxOC8zMzQzMDM2MDAtNzZhNzNmMmEtNjg1ZC00NjNhLWI4ODEtMWM5YTk4ZGRkODE1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODIzVDIwMTY1NFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWU4OTRkYWIyMWY0MGUyZDBkNGNlZjExMGYxMTFmOGM0MGNkYWRkZmU3MDJjYmQxNTgyN2M4MDIyN2FkZjcxM2ImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.28CFMpK_HooqjR_iVKis0AKJlUPcbw-6UzLSP4iPiqw)
Environments
The text was updated successfully, but these errors were encountered: