8000 shm-sync fails with "Segmantation fault" · Issue #17 · goldsborough/ipc-bench · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

shm-sync fails with "Segmantation fault" #17

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.

Sign up for GitHub

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

Jump to bottom
Open
betulum opened this issue Jun 14, 2019 · 2 comments
Open

shm-sync fails with "Segmantation fault" #17

betulum opened this issue Jun 14, 2019 · 2 comments
Labels
bug

Comments

@betulum
Copy link
betulum commented Jun 14, 2019

both shm-server and shm-client fail with
"Segmentation fault (core dumped)"
@alexandervanrenen
Copy link
Collaborator

Hi betulum,

I am glad to see people using our project and thank you for pointing out these issues. However, we don't really work on this anymore and it is therefore unlikely to be fixed by us.

What I would suggest is to use/have a look at L5 (https://github.com/pfent/L5RDMA) instead. It is basically the continuation of this project. We dropped some communication protocols (which were identified to be slow in this project) and improved the libraries interface. It offers RDMA and TCP for remote and Domain Sockets and Shared Memory for local. And: it is actively being used at our university, so any bugs are likely to be fixed :)

If you really want to play around with some of the slower techniques (pipes, fifos ..), you are also welcome to try to add them to L5 ;)

Best of luck with wich ever way you go.

  • alex

@mslijepc
Copy link

I also tried running shm-sync and it didn't finish, didn't get a seg fault message either. Was debugging, but now I saw this issue. @betulum thatnks for reporting this.

@alexandervanrenen I will check the L5 project now. I would like to run two process in lock-step, which mechanism you think from L5 would be the fastest?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
335D
Development

No branches or pull requests
3 participants
@alexandervanrenen @betulum @mslijepc
0