From: "M.T." <xzavierpower@gmail.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Shell App hangs on exit
Date: Tue, 12 Jul 2022 14:05:55 -0400 [thread overview]
Message-ID: <CAEsd5Ruro_qkEqD8AOpHaYt3pqZ3-KBhmmW_-zKrA3Efpu=aKw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
Hello folks
I'm facing a bit of a weird issue here.
I'm working on a UEFI shell app, which, for some reason, hangs on exit, and
by that I mean when I'm returning the final status from ShellAppMain.
ie:
INTN EFIAPI ShellAppMain( IN UINTN Argc, IN CHAR16 **Argv)
{
EFI_STATUS status;
...
return status;
}
Looking through other examples, all other shell apps do exactly the same
thing, yet mine hangs every time without fail.
I suspect it might have something to do with memory that was not freed, but
that is just a suspicion for now as I had it exiting properly not that long
ago.
Question here is, how can I figure out what is going on?
Are there any code analysis tools I could try?
Normally I would use something like valgrind, but I am not sure
anything like it exists for UEFI shell.
Appreciate any help.
Thank you
xp
[-- Attachment #2: Type: text/html, Size: 1105 bytes --]
reply other threads:[~2022-07-12 18:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEsd5Ruro_qkEqD8AOpHaYt3pqZ3-KBhmmW_-zKrA3Efpu=aKw@mail.gmail.com' \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox