Opened 9 years ago
Closed 8 years ago
#11428 closed enhancement (fixed)
More secure string handling
| Reported by: | Karvjorm | Owned by: | bonefish |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Build System | Version: | R1/Development |
| Keywords: | bluetooth headers | Cc: | |
| Blocked By: | Blocking: | #11427 | |
| Platform: | All |
Description
Here are two bluetooth header file enchancements.
Attachments (1)
Change History (5)
by , 9 years ago
| Attachment: | blue.patch added |
|---|
comment:1 by , 9 years ago
| Blocking: | 11427 added |
|---|
comment:2 by , 9 years ago
| patch: | 0 → 1 |
|---|
comment:3 by , 9 years ago
| Milestone: | R1 → Unscheduled |
|---|
comment:4 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixed the actual problem in hrev50088. The comment was not referring to the string length (not a problem, the used format string would lead to a fixed format), but to the fact that the static variables used were not thread safe.
Note:
See TracTickets
for help on using tickets.
Why is this not using BString::SetToFormat instead?
Moving out of R1: bluetooth is not included there.