From: Arka Sharma <arka.sw1988@gmail.com>
To: edk2-devel@lists.01.org
Subject: NvmExpressDxe async application crash with UDK debugger
Date: Wed, 12 Apr 2017 10:28:57 +0530 [thread overview]
Message-ID: <CAPO=kN11yk0TbqxxkZktB6HySwFnN5VQWE7h78N_XrC4kaFyug@mail.gmail.com> (raw)
Hi,
I am testing async io in NvmExpressDxe. The target system is Asrock
Z97 which I have connected to host with serial port where UDK debugger
is running. So my application does following
1. CreateEvent
2. Call Passthru
3. CmdSent++;
4. Repeat 1-3 until not ready from driver
5. while (CmdRecd < CmdSent);
4. Close all the events.
CmdRecvd is incremented inside EventCallback. I am allocating both
CmdSent and CmdRecvd and passing the address of CmdRecvd in
CreateEvent. With this I face WinDbg exception quite often and it says
"Target encountered an exception: Vector = 6, Error Code = 00000000".
I can share the application code for more clarity. I am building with
/Od and GenFw with --keepexceptiontable
Regards,
Arka
next reply other threads:[~2017-04-12 4:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 4:58 Arka Sharma [this message]
2017-04-12 5:07 ` NvmExpressDxe async application crash with UDK debugger Tian, Feng
2017-04-12 6:05 ` Arka Sharma
2017-04-13 5:46 ` Wu, Hao A
2017-04-17 12:54 ` Arka Sharma
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='CAPO=kN11yk0TbqxxkZktB6HySwFnN5VQWE7h78N_XrC4kaFyug@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