Bug #945
OscReceiver segfaults if port is busy
| Status: | Closed | Start date: | 2012-08-08 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | - | Spent time: | - | |
| Target version: | 0.4 | |||
| Version: | 0.1 |
History
Updated by Alexandre Quessy 10 months ago
- Target version set to 0.2
- Version set to 0.1
Updated by Alexandre Quessy 10 months ago
- Target version changed from 0.2 to 0.6
Updated by Alexandre Quessy 8 months ago
- Target version changed from 0.6 to 0.2
Updated by Alexandre Quessy 8 months ago
- Assignee changed from Alexandre Quessy to Louis Bouchard
Updated by Alexandre Quessy 8 months ago
- Priority changed from Normal to High
Updated by Alexandre Quessy 7 months ago
- Target version changed from 0.2 to 0.4
Updated by Alexandre Quessy 5 months ago
- Assignee changed from Louis Bouchard to Alexandre Quessy
See in OSCrxtx or SPIN to check if the receiving port is busy. (or to receive the same messages within two different osc receiver nodes)
Updated by Alexandre Quessy 3 months ago
- Status changed from New to Closed
We were using the osc server object even if NULL.