Moths ago, I posted a an email upstream to report a problem when I analyzed kernel coredump on DM code using crash tool. Here is the question:html
[dm-devel] [Report] crash tool cannot resolve struct dm_table properlyapp
which is archived here:post
https://www.redhat.com/archives/dm-devel/2017-April/msg00197.htmlui
Shortly, Steffen Maier replied with the following workaround:this
As workaround for eppic scripts in crash, we currently re-define struct dm_table in eppic scripts, because "set scope dm_table_create" has not always worked as we liked. Sometimes "whatis dm_table_create" and again "set scope dm_table_create" worked and we put this in .crashrc, but eventually gave up and kept our struct re-define.
A workaround for this problem:code
Before we wrote above posting, we tried this; maybe it helps in your case: crash> set gdb on gdb: on gdb> ptype struct dm_table type = struct dm_table { int undefined__; } gdb> ptype 'drivers/md/dm-table.c'::dm_table No symbol "dm_table" in specified context. gdb: gdb request failed: ptype 'drivers/md/dm-table.c'::dm_table gdb> ptype struct dm_table type = struct dm_table { uint64_t features; struct mapped_device *md; unsigned int type; ...