Re: [Valgrind-users] bug report: bugzilla refused to accept this saying it contains spam. But it doesn't.

[ISHIKAWA,chiaki <ish...@yk...>]

On 2022/09/23 9:11, John Reiser wrote:
>> I think valgrind experienced a division by zero.
>>
>> readdwarf.c:
>>
>>        if (op_code >= info.li_opcode_base) {
>>           op_code -= info.li_opcode_base;
>>           Word adv = (op_code / info.li_line_range)    <--- line 831
>>                         * info.li_min_insn_length;
>>           Int advAddr = adv;
>>           state_machine_regs.address += adv;
>
> If you can re-build valgrind, then a quick-and-dirty work-around
> might be
>
> >           Word adv = (op_code / (info.li_line_range ?: 1))
> >                         * info.li_min_insn_length;
>
> where "x ?: y" is a deprecated-but-useful slang for "x ? x : y".
>
> Also, one probable reason for the bug reporting system rejecting
> your first submission is the many consecutive lines that begin with
> "00:08.54 GECKO(319869) ".  The work-around for this is to put
> the text of the valgrind complaint into an attachment, and say
> "See the attachment for the full text of the valgrind complaint."



Thank you for the comment.


I will try to re-submit the bugzilla entry.

I didn't realize the lines starting with timestamp string such as 
""00:08.54 GECKO(319869) " causing the problem.
I thought there were no URLs, and so no spam. :-)

Sorry, somehow I overlooked your e-mail and thus this very tardy response.

TIA

Chiaki