29.11.2012 09:36, Angus Salkeld wrote:
...
>>> so, qb_array_index() fails once idx spans uint16_t boundary (0x) and
>>> (uint16_t)idx > 0.
>>> IMHO this naturally means some kind of integer overflow.
>>
>> Well done, I'll have a closer look at it.
>
> Patch here:
> https://github.com/asalkeld/
On 29/11/12 10:15 +1100, Angus Salkeld wrote:
On 27/11/12 09:34 +0300, Vladislav Bogdanov wrote:
22.11.2012 14:18, Angus Salkeld wrote:
On 22/11/12 11:48 +1100, Andrew Beekhof wrote:
On Tue, Nov 20, 2012 at 5:32 PM, Vladislav Bogdanov
wrote:
Hi,
Running 06229e9 with qb 0.14.3, and noticed f
On 27/11/12 09:34 +0300, Vladislav Bogdanov wrote:
22.11.2012 14:18, Angus Salkeld wrote:
On 22/11/12 11:48 +1100, Andrew Beekhof wrote:
On Tue, Nov 20, 2012 at 5:32 PM, Vladislav Bogdanov
wrote:
Hi,
Running 06229e9 with qb 0.14.3, and noticed following assert() in trace
logging path:
#0 0
22.11.2012 14:18, Angus Salkeld wrote:
> On 22/11/12 11:48 +1100, Andrew Beekhof wrote:
>> On Tue, Nov 20, 2012 at 5:32 PM, Vladislav Bogdanov
>> wrote:
>>> Hi,
>>>
>>> Running 06229e9 with qb 0.14.3, and noticed following assert() in trace
>>> logging path:
>>>
>>> #0 0x7f40451688a5 in raise
On 22/11/12 14:37 +0300, Vladislav Bogdanov wrote:
22.11.2012 14:18, Angus Salkeld wrote:
On 22/11/12 11:48 +1100, Andrew Beekhof wrote:
On Tue, Nov 20, 2012 at 5:32 PM, Vladislav Bogdanov
wrote:
Hi,
Running 06229e9 with qb 0.14.3, and noticed following assert() in trace
logging path:
#0 0
On Fri, Nov 23, 2012 at 10:20 AM, Angus Salkeld wrote:
> On 22/11/12 14:37 +0300, Vladislav Bogdanov wrote:
>>
>> 22.11.2012 14:18, Angus Salkeld wrote:
>>>
>>> On 22/11/12 11:48 +1100, Andrew Beekhof wrote:
On Tue, Nov 20, 2012 at 5:32 PM, Vladislav Bogdanov
wrote:
>
> Hi,
On 22/11/12 14:37 +0300, Vladislav Bogdanov wrote:
22.11.2012 14:18, Angus Salkeld wrote:
On 22/11/12 11:48 +1100, Andrew Beekhof wrote:
On Tue, Nov 20, 2012 at 5:32 PM, Vladislav Bogdanov
wrote:
Hi,
Running 06229e9 with qb 0.14.3, and noticed following assert() in trace
logging path:
#0 0
On Thu, Nov 22, 2012 at 10:37 PM, Vladislav Bogdanov
wrote:
> log_dcs.c:70 is assert(rc == 0);
> So, qb_array_index() returns 0
>
> Couldn't that be some integer overflow?
Sounds plausible.
Certainly everything we're passing to libqb looks valid.
___
22.11.2012 14:18, Angus Salkeld wrote:
> On 22/11/12 11:48 +1100, Andrew Beekhof wrote:
>> On Tue, Nov 20, 2012 at 5:32 PM, Vladislav Bogdanov
>> wrote:
>>> Hi,
>>>
>>> Running 06229e9 with qb 0.14.3, and noticed following assert() in trace
>>> logging path:
>>>
>>> #0 0x7f40451688a5 in raise
On 22/11/12 11:48 +1100, Andrew Beekhof wrote:
On Tue, Nov 20, 2012 at 5:32 PM, Vladislav Bogdanov
wrote:
Hi,
Running 06229e9 with qb 0.14.3, and noticed following assert() in trace
logging path:
#0 0x7f40451688a5 in raise () from /lib64/libc.so.6
#1 0x7f404516a085 in abort () from
On Tue, Nov 20, 2012 at 5:32 PM, Vladislav Bogdanov
wrote:
> Hi,
>
> Running 06229e9 with qb 0.14.3, and noticed following assert() in trace
> logging path:
>
> #0 0x7f40451688a5 in raise () from /lib64/libc.so.6
> #1 0x7f404516a085 in abort () from /lib64/libc.so.6
> #2 0x7f4045161
Hi,
Running 06229e9 with qb 0.14.3, and noticed following assert() in trace
logging path:
#0 0x7f40451688a5 in raise () from /lib64/libc.so.6
#1 0x7f404516a085 in abort () from /lib64/libc.so.6
#2 0x7f4045161a1e in __assert_fail_base () from /lib64/libc.so.6
#3 0x7f4045161ae0
12 matches
Mail list logo