public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
* ShellPkg: Difference in behavior of 'dh' between old shell and new
@ 2017-04-19 17:36 Jeff Westfahl
  2017-04-19 17:48 ` Carsey, Jaben
  0 siblings, 1 reply; 4+ messages in thread
From: Jeff Westfahl @ 2017-04-19 17:36 UTC (permalink / raw)
  To: edk2-devel; +Cc: jaben.carsey, ruiyu.ni

I noticed a difference in behavior of 'dh' between the old shell and the 
new shell. With the old shell, 'dh -v' for a LoadedImage handle shows the 
following:

Handle D3 (3A537F98)
    Image (3A532818)   File:MicrocodeUpdate
      ParentHandle..: 3A64F118
      SystemTable...: 3D2A8F18
      DeviceHandle..: 3B1B2098
      FilePath......: FvFile(F3331DE6-4A55-44E4-B767-7453F7A1A021)
      ImageBase.....: 3D650000 - 3D655540
      ImageSize.....: 5540
      CodeType......: RT_code
      DataType......: RT_data

With the new shell, I get this for the same LoadedImage handle:

D3: 3A537F98
LoadedImage
      Revision......: 0x00001000
      ParentHandle..: 3A64F118
      SystemTable...: 3D2A8F18
      DeviceHandle..: 3B1B2098
      FilePath......: 3A539018
      OptionsSize...: 0
      LoadOptions...: 0
      ImageBase.....: 3D650000
      ImageSize.....: 5540
      CodeType......: EfiRuntimeServicesCode
      DataType......: EfiRuntimeServicesData
      Unload........: 0

The old shell shows the name of the file associated with the LoadedImage, 
which seems like useful information. Is this omission intentional or an 
oversight? Would a patch adding the file name to ShellPkg be welcomed?

Regards,
Jeff


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2017-05-04 16:31 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-04-19 17:36 ShellPkg: Difference in behavior of 'dh' between old shell and new Jeff Westfahl
2017-04-19 17:48 ` Carsey, Jaben
2017-05-04 14:59   ` Jeff Westfahl
2017-05-04 16:31     ` Carsey, Jaben

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox