Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

cannot set scope for dm_table_create without prior whatis

Version-Release number of selected component (if applicable):

crash 8.0.0-6.el9
issue also reproducible on latest upstream crash (head at bdbf5887d6259ea3108d4fa674f3794adad54d52)

How reproducible:

every time in provided core

Steps to Reproduce:

# crash vmcore.vmsn vmlinux

crash> mod -S usr/lib/debug/lib/modules/3.10.0-229.el7.x86_64

crash> set scope dm_table_create
set: gdb cannot find text block for address: dm_table_create

crash> whatis dm_table_create
int dm_table_create(struct dm_table **, fmode_t, unsigned int, struct mapped_device *);

crash> set scope dm_table_create
scope: ffffffffa0005380 (dm_table_create)

Actual results:

set scope fails first time

Expected results:

set scope should work the first time ; whatis should be unneeded

Hi Lijiang; thanks so much.  Yes the mod -rS works around the issue.  Should the first mod command run on a core go through the readnow path?

(In reply to John Pittman from comment #3)
> Hi Lijiang; thanks so much.  Yes the mod -rS works around the issue.  Should
> the first mod command run on a core go through the readnow path?

The '-r' option will cause the GDB to read the full symbol file, it may be slower. Most of time, it is not needed.

I would suggest closing this issue as WON'T because it can work well with the '-r' option, and this doesn't affect the debugging.

Thanks.

Thanks; why does the whatis command fix the issue?

(In reply to John Pittman from comment #5)
> Thanks; why does the whatis command fix the issue?

The 'whatis' and 'ptype' can passthrough the gdb, eventually they will call the whatis_exp() in gdb, which will parse expression, this operation may affect the SYMTAB BLOCK and symbol search. If you are interested, you could refer to the parse_exp_in_context().

Thanks.