Bug 1839850

I'm not sure what's causing the set command to act differently, but I copied the
vmlinux/vmcore pair and the target module object file locally.  First I loaded it
without -readnow (mod -s), and the set scope fails.  I then delete the module, and
reload it with -readnow (mod -rs), and the set scope works OK.  I ran "sys", and all
subsequent set scope operations work OK:

  $ crash vmlinux vmcore
  
  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...
  
  WARNING: kernel relocated [58MB]: patching 85605 gdb minimal_symbol values
  
        KERNEL: vmlinux                                                  
      DUMPFILE: vmcore  [PARTIAL DUMP]
          CPUS: 48
          DATE: Sat Aug  3 11:41:00 2019
        UPTIME: 1 days, 10:28:48
  LOAD AVERAGE: 2.95, 1.02, 0.40
         TASKS: 1060
      NODENAME: iop053063.lss.emc.com
       RELEASE: 3.10.0-957.el7.x86_64
       VERSION: #1 SMP Thu Oct 4 20:48:51 UTC 2018
       MACHINE: x86_64  (2999 Mhz)
        MEMORY: 127.9 GB
         PANIC: "SysRq : Trigger a crash"
           PID: 189250
       COMMAND: "bash"
          TASK: ffff924c30e3a080  [THREAD_INFO: ffff924c133c0000]
           CPU: 5
         STATE: TASK_RUNNING (SYSRQ)
  
  crash> mod -s dm_service_time
       MODULE       NAME                            SIZE  OBJECT FILE
  ffffffffc044f0a0  dm_service_time                12889  /home/anderson/dm-service-time.ko.debug 
  crash> set scope st_create
  set: gdb cannot find text block for address: st_create
  crash> mod -d dm_service_time
  crash> mod -sr dm_service_time
       MODULE       NAME                            SIZE  OBJECT FILE
  ffffffffc044f0a0  dm_service_time                12889  /home/anderson/dm-service-time.ko.debug 
  crash> set scope st_create
  scope: ffffffffc044d270 (st_create)
  crash> sys
        KERNEL: vmlinux
      DUMPFILE: vmcore  [PARTIAL DUMP]
          CPUS: 48
          DATE: Sat Aug  3 11:41:00 2019
        UPTIME: 1 days, 10:28:48
  LOAD AVERAGE: 2.95, 1.02, 0.40
         TASKS: 1060
      NODENAME: iop053063.lss.emc.com
       RELEASE: 3.10.0-957.el7.x86_64
       VERSION: #1 SMP Thu Oct 4 20:48:51 UTC 2018
       MACHINE: x86_64  (2999 Mhz)
        MEMORY: 127.9 GB
         PANIC: "SysRq : Trigger a crash"
  crash> set scope st_create
  scope: ffffffffc044d270 (st_create)
  crash>

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (crash bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4199