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

Assertion `status == 0’ failed #82

Open
mwittig opened this issue Mar 11, 2019 · 4 comments
Open

Assertion `status == 0’ failed #82

mwittig opened this issue Mar 11, 2019 · 4 comments

Comments

@mwittig
Copy link
Contributor

mwittig commented Mar 11, 2019

node: …/src/binding.cc:186: static void Pcap::cb_packets(uv_poll_t*, int, int): Assertion `status == 0’ failed.

I think, socket errors need to be properly handled similar to the cases reported earlier. See #23 and #26

@mscdex
Copy link
Owner

mscdex commented Mar 11, 2019

Can you provide a reproducible test for this? What platform did you encounter this on?

@mwittig
Copy link
Contributor Author

mwittig commented Mar 14, 2019

Sorry for the delay in reply. The platform is:

libpcap 1.6.2-2
Linux raspberrypi 4.9.35-v7+

I am using cap as part of complex application. Thus I'll try to to create an isolated test case.

Generally, I am wondering why status != 0 isn't handled gracefully. Is it really a pathological case? A similar assertion issue had occurred on Windows earlier. See #23 and #26

@mscdex
Copy link
Owner

mscdex commented Mar 14, 2019

What node version and cap version are you using?

@mscdex
Copy link
Owner

mscdex commented Mar 14, 2019

Also, does simply commenting out the offending line out fix the issue or cause other problems? It would be interesting to know what the status value is when it's not zero.... it should correspond to an libuv error.

mwittig added a commit to mwittig/cap that referenced this issue Apr 11, 2019
Giuan0 pushed a commit to Giuan0/cap that referenced this issue Jul 5, 2019
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