Tim,
I'm sure that it the requirement were added to the UEFI Shell specification it
would soon appear in the code.
I don't work on the UEFI Shell so I can't say what may or may not happen in the
future.
Technically, your suggestion is feasible. This is similar to what is planned
for StdLib. All SFS protocol file systems are found, sorted by device path in
the same way the UEFI Shell does it, and the CWD is set to the root of that
file system.
Daryl McDaniel
"There's a band called 1023MB. They haven't had any gigs yet."
From: Tim Lewis [mailto:tim.le...@insyde.com]
Sent: Tuesday, July 02, 2013 10:52 AM
To: Mcdaniel, Daryl; ritul guru (riguru); Toto Lebolo;
edk2-devel@lists.sourceforge.net
Subject: RE: [edk2] assertion "tmp != NULL" failed: file "sys\open.c", line 171
Daryl - If the shell is launched from a device that has a mapping, could we set
CWD to something other than nothing? For example, the location where
startup.nsh is located?
Tim
From: Mcdaniel, Daryl [mailto:daryl.mcdan...@intel.com]
Sent: Tuesday, July 02, 2013 10:48 AM
To: ritul guru (riguru); Toto Lebolo; edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] assertion "tmp != NULL" failed: file "sys\open.c", line 171
This error is produced by the OLD EFI toolkit.
It results because the current working directory is not set. The ASSERT is
triggered specifically because CWD does not contain a ':'.
Within either the EFI or UEFI shells, CWD is not set until after the first time
one explicitly sets it. For example, the initial prompt from the Shell is
"Shell> ". If you see this prompt, there is NO CWD. If you then switch to one
of the mapped drives, say fs0, then CWD will be set for that volume. Example:
Shell> fs0:
fs0:\>
After the above sequence, the CWD will be the root, "\", of volume "fs0".
Daryl McDaniel
"I have always wished for my computer to be as easy to use as my telephone;
my wish has come true because I can no longer figure out how to use my
telephone."
-- Bjarne Stoustrup
From: ritul guru (riguru) [mailto:rig...@cisco.com]
Sent: Monday, July 01, 2013 10:58 PM
To: Toto Lebolo;
edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: Re: [edk2] assertion "tmp != NULL" failed: file "sys\open.c", line 171
+1,
I have also seen this issue, when I was using open() function of libc in one of
the efi application.
But I couldn't find the reason behind this.
Regards,
Ritul
From: Toto Lebolo [mailto:toto_leb...@yahoo.com]
Sent: Tuesday, July 02, 2013 4:35 AM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: [edk2] assertion "tmp != NULL" failed: file "sys\open.c", line 171
I am getting this error message in the shell when invoking the python
interpreter or when launching the ftp command.
I don't know why I am getting this error message. I remember that Python was
running fine few months ago.
I cannot find what is causing this error.
Does anybody experience this issue?
The error message: "assertion "tmp != NULL" failed: file "sys\open.c", line 171"
Thanks for the help.
MiKL~
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
