public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Kumar N, Bhuvanendra" <Bhuvanendra.KumarN@amd.com>
To: Joel Brobecker <brobecker@adacore.com>,
	Andrew Burgess <aburgess@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"George, Jini Susan" <JiniSusan.George@amd.com>,
	"Achra, Nitika" <Nitika.Achra@amd.com>,
	"Sharma, Alok Kumar" <AlokKumar.Sharma@amd.com>,
	"E, Nagajyothi" <Nagajyothi.E@amd.com>,
	Andrew Burgess <aburgess@redhat.com>
Subject: RE: [PATCH] Fix ptype and print commands for namelist variables(a fortran feature)
Date: Thu, 23 Dec 2021 15:51:44 +0000	[thread overview]
Message-ID: <MW2PR12MB46845725FF8AE46602686428877E9@MW2PR12MB4684.namprd12.prod.outlook.com> (raw)
In-Reply-To: <YcAQ9qkfOqdIV4zB@adacore.com>

[AMD Official Use Only]

Hi,

I could reproduce the assert that Andrew mentioned with the patch and -D_GLIBCXX_DEBUG=1. I am looking into it.

I had to configure like this as Andrew suggested.

../binutils-gdb/configure  --disable-sim --enable-targets=all CFLAGS="-O0 -g3 -D_GLIBCXX_DEBUG=1" CXXFLAGS="-O0 -g3 -D_GLIBCXX_DEBUG=1"

Regards,
Bhuvan

-----Original Message-----
From: Joel Brobecker <brobecker@adacore.com> 
Sent: Monday, December 20, 2021 10:43 AM
To: Kumar N, Bhuvanendra <Bhuvanendra.KumarN@amd.com>
Cc: Joel Brobecker <brobecker@adacore.com>; gdb-patches@sourceware.org; George, Jini Susan <JiniSusan.George@amd.com>; Achra, Nitika <Nitika.Achra@amd.com>; Sharma, Alok Kumar <AlokKumar.Sharma@amd.com>; E, Nagajyothi <Nagajyothi.E@amd.com>; Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH] Fix ptype and print commands for namelist variables(a fortran feature)

[CAUTION: External Email]

Hi Bhuvan,

> Thanks a lot for your comments. I have tried to address all your 
> previous comments. I have attached the revised patch and also inlined.
> Not sure if you see some trailing spaces or indentation issues still, 
> mostly they are due to my email client(MS outlook). Please let me know 
> if you have any comments. Thanks again.

I believe Andrew had some questions (failed assertion).
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceware.org%2Fpipermail%2Fgdb-patches%2F2021-December%2F184362.html&amp;data=04%7C01%7CBhuvanendra.KumarN%40amd.com%7C0e5d2c316a6743220b7908d9c3777633%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637755740127814129%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=7FIqu1y2JDqVzKKGbOpSS0qOBfZQdofAmYvOYM%2BS2Wk%3D&amp;reserved=0

Have you looked into that?

--
Joel

  reply	other threads:[~2021-12-23 15:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24  9:16 Kumar N, Bhuvanendra
2021-08-24  9:21 ` Kumar N, Bhuvanendra
2021-09-20  9:41 ` Andrew Burgess
2021-09-22 12:38   ` Kumar N, Bhuvanendra
2021-10-06 15:51     ` Andrew Burgess
2021-10-07 21:05       ` Kumar N, Bhuvanendra
2021-10-18 17:02         ` Kumar N, Bhuvanendra
2021-11-04 15:50         ` Andrew Burgess
2021-11-19 14:09         ` FW: " Kumar N, Bhuvanendra
2021-11-19 14:32           ` Kumar N, Bhuvanendra
2021-12-03 18:56             ` Kumar N, Bhuvanendra
2021-12-04 13:20               ` Joel Brobecker
2021-12-10 16:18                 ` Kumar N, Bhuvanendra
2021-12-20  5:13                   ` Joel Brobecker
2021-12-23 15:51                     ` Kumar N, Bhuvanendra [this message]
2022-01-20 16:20                       ` Kumar N, Bhuvanendra
2022-02-03 18:43                         ` Andrew Burgess
2022-02-07 14:41                           ` Kumar N, Bhuvanendra
2022-02-11 16:20                             ` Andrew Burgess
2022-02-11 16:39                               ` Kumar N, Bhuvanendra
2021-12-09 13:16             ` Andrew Burgess

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=MW2PR12MB46845725FF8AE46602686428877E9@MW2PR12MB4684.namprd12.prod.outlook.com \
    --to=bhuvanendra.kumarn@amd.com \
    --cc=AlokKumar.Sharma@amd.com \
    --cc=JiniSusan.George@amd.com \
    --cc=Nagajyothi.E@amd.com \
    --cc=Nitika.Achra@amd.com \
    --cc=aburgess@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).