Source Activity

Namely for [s]size_t, [{phys|generic}_]addr_t and off_t. Namely for [s]size_t, [{phys|generic}_]addr_t and off_t.

Putting the add-ons uses the dormant node manager of the BMediaRoster. The BMediaRoster must therefore only be quit after all add-ons are put. Putting the add-ons uses the dormant node manager of the BMediaRoster. The BMediaRoster must therefore only be quit after all add-ons are put.

The hash table member still uses the element array memeber to clear itself on destruction. We must therefore ensure that the element array isn't destroyed before the hash table. Since the destruction order of memebers is the reverse order of their declaration, reordering them is enough. The hash table member still uses the element array memeber to clear itself on destruction. We must therefore ensure that the element array isn't destroyed before the hash table. Since the destruction order of memebers is the reverse order of their declaration, reordering them is enough.

The BShelf sets itself as a handler on the containing view on creation but didn't unset itself on destruction. When the containing view was later destroyed it would unset the shelf which triggered a use-after-free if you deleted the BShelf beforehand. Since the ownership of a BShelf isn't explicitly documented I took the shelf in DeskWindow of Tracker as a reference, which does delete it explicitly. The BShelf sets itself as a handler on the containing view on creation but didn't unset itself on destruction. When the containing view was later destroyed it would unset the shelf which triggered a use-after-free if you deleted the BShelf beforehand. Since the ownership of a BShelf isn't explicitly documented I took the shelf in DeskWindow of Tracker as a reference, which does delete it explicitly.

The inner loop to skip the function declaration stops at the terminating null but didn't break out of the loop in that case, causing the outer loop increment to skip the terminator and read beyond the string end. Well formatted symbols do not trigger this, but there sometimes are false positives that would cause it to happen. It was seen in Debugger that reuses this code. The inner loop to skip the function declaration stops at the terminating null but didn't break out of the loop in that case, causing the outer loop increment to skip the terminator and read beyond the string end. Well formatted symbols do not trigger this, but there sometimes are false positives that would cause it to happen. It was seen in Debugger that reuses this code.

* CID 1251065. * CID 1251065.