On 11/25/2015 03:18 AM, Markus Armbruster wrote:
> John Snow writes:
>
>> Trivial: this array should be allocated to have ID_MAX entries always.
>> Otherwise if someone were to forget to expand this table, the assertion
>> in the id generator won't actually trigger; it will read junk data.
>
>
Kevin Wolf writes:
> Am 25.11.2015 um 09:18 hat Markus Armbruster geschrieben:
>> John Snow writes:
>>
>> > Trivial: this array should be allocated to have ID_MAX entries always.
>> > Otherwise if someone were to forget to expand this table, the assertion
>> > in the id generator won't actually
Am 25.11.2015 um 09:18 hat Markus Armbruster geschrieben:
> John Snow writes:
>
> > Trivial: this array should be allocated to have ID_MAX entries always.
> > Otherwise if someone were to forget to expand this table, the assertion
> > in the id generator won't actually trigger; it will read junk
John Snow writes:
> Trivial: this array should be allocated to have ID_MAX entries always.
> Otherwise if someone were to forget to expand this table, the assertion
> in the id generator won't actually trigger; it will read junk data.
You mean this one:
assert(id < ID_MAX);
The assertion i
Trivial: this array should be allocated to have ID_MAX entries always.
Otherwise if someone were to forget to expand this table, the assertion
in the id generator won't actually trigger; it will read junk data.
Signed-off-by: John Snow
---
util/id.c | 2 +-
1 file changed, 1 insertion(+), 1 dele
