m
Cc: edk2-devel@lists.01.org
Subject: Re: [edk2] UEFI Shell Lib Constructor and Shell Parameters Protocol
Thanks, Jaben. That makes sense.
Now I see the real issue is with the "app" I ran across. It is a driver, and
it was trying to access command line args. The driver crashed when i
om
> Sent: Wednesday, April 05, 2017 8:21 AM
> To: Carsey, Jaben ; Ni, Ruiyu
> Cc: edk2-devel@lists.01.org
> Subject: Re: [edk2] UEFI Shell Lib Constructor and Shell Parameters Protocol
> Importance: High
>
> Thanks, Jaben. That makes sense.
>
> Now I see the real issue is w
M
> To: Carsey, Jaben ; Ni, Ruiyu
> Cc: edk2-devel@lists.01.org
> Subject: [edk2] UEFI Shell Lib Constructor and Shell Parameters Protocol
> Importance: High
>
>
> A question or two for all shell experts:
>
> In the UEFI Shell Lib constructor code, if the Shell
mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> jim.dai...@dell.com
> Sent: Wednesday, April 05, 2017 7:07 AM
> To: Carsey, Jaben ; Ni, Ruiyu
> Cc: edk2-devel@lists.01.org
> Subject: [edk2] UEFI Shell Lib Constructor and Shell Parameters Protocol
> Importance: High
>
>
A question or two for all shell experts:
In the UEFI Shell Lib constructor code, if the Shell protocol cannot
be opened, then an attempt is made to locate it before "giving up".
However, if the Shell parameters protocol cannot be opened, no attempt
is made to locate it---the code simply leaves t
5 matches
Mail list logo
