On 2024/04/02 16:29, Tao Liu wrote:
> Hi Naveen,
>
> On Tue, Apr 2, 2024 at 3:17 PM Naveen Chaudhary
> wrote:
>>
>> Thanks Tao,
>>
>> On a funny side, though I didn't understand this area of code much, but I
>> ironically made the exact same fix to avoid problem for time being on my
>> side,
I am analyzing the kdump in latest crash utility 8.0.4++.
I think I loaded the module symbols correctly :
crash> mod
MODULE NAME TEXT_BASE SIZE OBJECT FILE
80007a7e2040 npdereference 80007a7e 12288 (not loaded)
[CONFIG_KALLSYMS]
crash>
crash> mod
Thanks Tao,
On a funny side, though I didn't understand this area of code much, but I
ironically made the exact same fix to avoid problem for time being on my side,
thinking there might be a different fix coming . Glad its now taken care.
Thanks
Regards,
Naveen
Hi Lianbo,
On Wed, Mar 6, 2024 at 2:32 PM Lianbo Jiang wrote:
>
> Some objects format may potentially support copy relocations, but
> currently the maybe_copied is always initialized to 0 in the symbol().
> And the type is 'mst_file_bss', not always the 'mst_bss' or 'mst_data'
> in the
Hi, Kazu and Tao
Could you please have a look? or Any comments?
Thanks
Lianbo
On 3/6/24 16:06, devel-requ...@lists.crash-utility.osci.io wrote:
Date: Wed, 6 Mar 2024 14:31:27 +0800
From: Lianbo Jiang
Subject: [Crash-utility] [PATCH] gdb: fix the "p" command incorrectly
print the
Hi Naveen,
On Tue, Apr 2, 2024 at 3:17 PM Naveen Chaudhary
wrote:
>
> Thanks Tao,
>
> On a funny side, though I didn't understand this area of code much, but I
> ironically made the exact same fix to avoid problem for time being on my
> side, thinking there might be a different fix coming .
Not all mod_mem_type will be included for kernel modules. E.g. in the
following module case:
(gdb) p lm->symtable[0]
$1 = (struct syment *) 0x4dcbad0
(gdb) p lm->symtable[1]
$2 = (struct syment *) 0x4dcbb70
(gdb) p lm->symtable[2]
$3 = (struct syment *) 0x4dcbc10
(gdb) p lm->symtable[3]
$4 =
