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

[TC-IDM-4.2]-While verifying the Activatation of the Subscription request messages, Chip-Tool aborted with a "Segmentation fault" during shutdown #15794

Closed
Rajashreekalmane opened this issue Mar 3, 2022 · 3 comments

Comments

@Rajashreekalmane
Copy link

Rajashreekalmane commented Mar 3, 2022

Problem

While verifying the response of the subscription request messages Chip-Tool aborted with a Segmentation fault.

Here is the example Execution Command: sudo ./chip-tool basic subscribe node-label 0 100 0 1 0

Setup:
Chip-Tool: RPI
DUT: RPI
Platform : IP and Wifi
Commit-ID:-883528dd3dadfcc665492be864866ad2e3889e16

PFA Screenshot:
image

PFA log below:-
Subscription log.txt

@Rajashreekalmane Rajashreekalmane changed the title [TC-IDM-4.2]-While verifying the Activatation the Subscription request messages, Chip-Tool aborted with a "Segmentation fault" [TC-IDM-4.2]-While verifying the Activatation of the Subscription request messages, Chip-Tool aborted with a "Segmentation fault" Mar 3, 2022
@bzbarsky-apple
Copy link
Contributor

@Rajashreekalmane Can you reproduce this reliably? If so, can you please run this under a debugger and get a stack and any other relevant information?

And in general, running things under the debugger all the time so you can get stacks and other information if they crash might be helpful...

@bzbarsky-apple bzbarsky-apple changed the title [TC-IDM-4.2]-While verifying the Activatation of the Subscription request messages, Chip-Tool aborted with a "Segmentation fault" [TC-IDM-4.2]-While verifying the Activatation of the Subscription request messages, Chip-Tool aborted with a "Segmentation fault" during shutdown Mar 4, 2022
@bzbarsky-apple
Copy link
Contributor

Also, it's possible this is the crash that #15816 was fixing....

@vivien-apple
Copy link
Contributor

#15914 is fixing one occurrence of a crash too. But "only" if the CASE connection has not been successfully set up, which may happens in the case where the node id is wrong for example.

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

4 participants