From: Bruce Richardson <bruce.richardson@intel.com>
To: "Menon, Ranjit" <ranjit.menon@intel.com>
Cc: Adham Masarwah <adham@mellanox.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Omar Cardona <ocardona@microsoft.com>,
Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>,
Jeffrey Tippet <Jeffrey.Tippet@microsoft.com>,
"Kadam, Pallavi" <pallavi.kadam@intel.com>,
Yohad Tor <yohadt@mellanox.com>,
Rani Sharoni <ranish@mellanox.com>,
Tal Shnaiderman <talshn@mellanox.com>
Subject: Re: [dpdk-dev] Generating Debug information in Windows using Clang (PDB files)
Date: Tue, 21 May 2019 09:22:12 +0100 [thread overview]
Message-ID: <20190521082211.GA1354@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <7603DC8746F9FC4D82EF0929C467267A736870C2@ORSMSX112.amr.corp.intel.com>
On Mon, May 20, 2019 at 07:02:22PM +0100, Menon, Ranjit wrote:
> Adham…
>
> I don’t think we debugged using clang compiled code for Hello world –
> mainly because it was only a “helloworld” application and we didn’t
> quite need any debugging!:-)
>
>
> I found this link:
> [1]http://blog.llvm.org/2017/08/llvm-on-windows-now-supports-pdb-debug.
> html
>
> …which says to use the following:
>
> Here are two simple ways to test out this new functionality:
> 1. Have clang-cl invoke lld automatically
>
> clang-cl -fuse-ld=lld -Z7 -MTd hello.cpp
> 2. Invoke clang-cl and lld separately.
>
> clang-cl -c -Z7 -MTd -o hello.obj hello.cpp
>
> lld-link -debug hello.obj
>
> Can you try it with just the -Z7 option?
>
>
> I’m also adding some persons from Microsoft to this thread, hoping they
> can help…
>
>
> +Harini +Omar +Jeffrey
>
>
> ranjit m.
>
Part of the issue may be that we use clang, rather than clang-cl on
windows.
/Bruce
next prev parent reply other threads:[~2019-05-21 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 10:27 Adham Masarwah
2019-05-20 18:02 ` Menon, Ranjit
2019-05-21 8:22 ` Bruce Richardson [this message]
2019-05-21 13:41 ` Adham Masarwah
2019-05-21 13:52 ` Bruce Richardson
2019-05-21 14:33 ` Adham Masarwah
2019-06-04 8:43 ` Thomas Monjalon
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-all 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=20190521082211.GA1354@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=Harini.Ramakrishnan@microsoft.com \
--cc=Jeffrey.Tippet@microsoft.com \
--cc=adham@mellanox.com \
--cc=dev@dpdk.org \
--cc=ocardona@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranish@mellanox.com \
--cc=ranjit.menon@intel.com \
--cc=talshn@mellanox.com \
--cc=yohadt@mellanox.com \
/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;
as well as URLs for NNTP newsgroup(s).