[Crash-utility] Trace common and ARM aarch64

[HAGIO KAZUHITO(萩尾 一仁)]

-----Original Message-----
> Hi folks at crash-utility,
> 
> I’m just hoping that this address still reaches you who support the crash utility.
> 
> I am having difficulty digging trace entries out of an ARM (aarch64) dump.
> I’m not sure whether the problem is in /sys/kernel/debug/trace or in the trace-cmd command.
> 
> Just using  trace-cmd extract, then this hangs: 
> # ./trace-cmd report 
> trace-cmd: No such file or directory 
>   [vmscan:mm_vmscan_writepage] function __builtin_constant_p not defined 
>   [scsi:scsi_dispatch_cmd_timeout] function scsi_trace_parse_cdb not defined 
>   [scsi:scsi_dispatch_cmd_start] function scsi_trace_parse_cdb not defined 
>   [scsi:scsi_dispatch_cmd_error] function scsi_trace_parse_cdb not defined 
>   [scsi:scsi_dispatch_cmd_done] function scsi_trace_parse_cdb not defined 
>   [ras:mc_event] function mc_event_error_type not defined 
> ^Ctrace-cmd: Received SIGINT 
> I have put debugging printf’s in trace-cmd and find it is hanging trying to parse entries in trace.dat.
> 
> This works okay on an x86_64 system at the same level.
> 
> The OS: # uname -a 
> Linux panda-aarch 5.3.18-24.46_6.0.29… 
> The trace-cmd is built from source, branch trace-cmd-stable-v2.6, which is the latest version I could
> successfully build.
> 
> Do you have any report of a problem with trace and trace-cmd specifically on aarch64?

at least I've not seen such report on this list and on the crash-trace's issues [1].

I've cc'd Hatayama-san, who is the maintainer.
Is there any information about this?

[1] https://github.com/fujitsu/crash-trace

Thanks,
Kazu