-
Notifications
You must be signed in to change notification settings - Fork 216
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
Concurrency issues? #14
Comments
I also recently got the following error: |
Hmm, thanks for reporting. Since mbusd is single-threaded application, re-entrancy shouldn't be an issue. I will look into it, but could you provide some context? What OS and hardware are you using (especially tty), also some info about client app and typical requests pattern. |
Linux 2.4.21-rmk1 #1 Mon Mar 5 15:00:39 CET 2012 armv4l unknown |
@dvader any updates on that? |
@3cky plz close that ticket |
I used to get crashes when logging "conn_open(): error in accept()", in particular, the call strerror(errno) crashes. After some reading it seems strerr is not re-entrant safe http://stackoverflow.com/questions/900338/why-cant-i-use-strerror. I am not sure if re-entrancy is the cause of the crash but after removing the function call and logging only errno, the software doesn't crash anymore.
However, it still sometimes get the error:
1485184829:392664 conn_open(): error in accept() (11)
1485184829:413938 tty: error in read() (11)
and sometimes only the accept error without the tty error.
I'll get the error more often if I use two clients to make requests.
I wonder if this error is caused by re-entrancy issues? Maybe there is a need to put mutexes on some function calls to make them thread safe?
The text was updated successfully, but these errors were encountered: