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

tox: new recipe for messaging platform (WIP, do not merge yet) #1076

Merged
merged 1 commit into from Jan 21, 2017

Conversation

scythx
Copy link
Contributor

@scythx scythx commented Jan 15, 2017

Adding new recipe for tox, an encrypted, P2P, messaging, audio/video calling platform.

@scythx
Copy link
Contributor Author

scythx commented Jan 15, 2017

Are you sure not facing kernel panic on --test? i still get it atm.

Adding new recipe for tox, an encrypted, P2P, messaging, audio/video calling platform.
@fbrosson
Copy link
Member

OMG, I also get the kernel crash when I run the tests!
I thought you were getting the crash when lauching the runtime. I had not tried the test before you mentioned it.

@scythx
Copy link
Contributor Author

scythx commented Jan 15, 2017

Yes the crash caused by encryptsave_test, tox_test, union_test, and dhf_test. still have no idea what caused it.

For encryptsave_test that's caused by something inside new_networking_ex.

@fbrosson fbrosson changed the title tox: new recipe for messaging platform tox: new recipe for messaging platform (WIP, do not merge yet) Jan 15, 2017
@scythx
Copy link
Contributor Author

scythx commented Jan 15, 2017

After some hours spending time to track the code flow, setsocketopt above return NULL; causes the kernel panic, still have no idea why this is happened and how to fix it since messenger_autotest use that block of code too but it doesn't crash.

screenshot from 2017-01-15 17-24-32

Ignore the return NULL; that's just my code to track the code flow.

removing thoose code solving the issue, but since remove to solve is a bad thing should i remove the code?
But some test would still failed.

@mmlr
Copy link
Member

mmlr commented Jan 15, 2017

KDLs are never the fault of the port (or porter) but always a bug in Haiku itself that should be taken up in the Haiku bug tracker at https://dev.haiku-os.org/ . Your last comment makes for a nice bug report as you've already narrowed the cause down significantly.

@pulkomandy pulkomandy merged commit d0dbdcb into haikuports:master Jan 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants