[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-devel] [bug #51990] Calling select() from different threads wi
From: |
Joel Cunningham |
Subject: |
Re: [lwip-devel] [bug #51990] Calling select() from different threads with MPU enabled triggers memory protection fault |
Date: |
Tue, 12 Sep 2017 14:11:59 -0500 |
> On Sep 12, 2017, at 1:35 PM, Simon Goldschmidt <address@hidden> wrote:
>
> Follow-up Comment #4, bug #51990 (project lwip):
>
> API_SELECT_CB_VAR_ALLOC() lets lwip_select() return ERR_MEM, I'll fix that and
> push it.
Good catch, should be setting errno and returning -1.
API_SELECT_CB_VAR_ALLOC_RETURN_NULL is unused and I don’t see a potential use
for it since select() can’t return NULL. Might want to remove it from the
change
Joel
- [lwip-devel] [bug #51990] Calling select() from different threads with MPU enabled triggers memory protection fault, David Lockyer, 2017/09/11
- [lwip-devel] [bug #51990] Calling select() from different threads with MPU enabled triggers memory protection fault, Joel Cunningham, 2017/09/11
- [lwip-devel] [bug #51990] Calling select() from different threads with MPU enabled triggers memory protection fault, Simon Goldschmidt, 2017/09/11
- [lwip-devel] [bug #51990] Calling select() from different threads with MPU enabled triggers memory protection fault, David Lockyer, 2017/09/12
- [lwip-devel] [bug #51990] Calling select() from different threads with MPU enabled triggers memory protection fault, Joel Cunningham, 2017/09/12
- [lwip-devel] [bug #51990] Calling select() from different threads with MPU enabled triggers memory protection fault, David Lockyer, 2017/09/12
- [lwip-devel] [bug #51990] Calling select() from different threads with MPU enabled triggers memory protection fault, Simon Goldschmidt, 2017/09/12
- Re: [lwip-devel] [bug #51990] Calling select() from different threads with MPU enabled triggers memory protection fault,
Joel Cunningham <=
- [lwip-devel] [bug #51990] Calling select() from different threads with MPU enabled triggers memory protection fault, Simon Goldschmidt, 2017/09/12
- [lwip-devel] [bug #51990] Calling select() from different threads with MPU enabled triggers memory protection fault, Joel Cunningham, 2017/09/13
- [lwip-devel] [bug #51990] Calling select() from different threads with MPU enabled triggers memory protection fault, Simon Goldschmidt, 2017/09/14
Re: [lwip-devel] [bug #51990] Calling select() from different threads with MPU enabled triggers memory protection fault, David Lockyer, 2017/09/12