On 10.10.2019 18:14, Jan Kiszka wrote:
> On 25.09.19 17:03, Joel Colledge wrote:
>> When CONFIG_PRINTK_CALLER is set, struct printk_log contains an
>> additional member caller_id. As a result, the offset of the log text is
>> different.
>>
>> This fixes the following error:
>>
>>(gdb) lx-dmesg
On 25.09.19 17:03, Joel Colledge wrote:
> When CONFIG_PRINTK_CALLER is set, struct printk_log contains an
> additional member caller_id. As a result, the offset of the log text is
> different.
>
> This fixes the following error:
>
> (gdb) lx-dmesg
> Python Exception embedded null character:
Hi Jan and Kieran, maintainers of scripts/gdb/,
CC: Leonard, most recent contributor to scripts/gdb/linux/dmesg.py
Could someone look at this fix please? Is there anything I should
improve in the code or the format of the contribution? Thanks.
When CONFIG_PRINTK_CALLER is set, struct printk_log contains an
additional member caller_id. As a result, the offset of the log text is
different.
This fixes the following error:
(gdb) lx-dmesg
Python Exception embedded null character:
Error occurred in Python command: embedded null charac
4 matches
Mail list logo