Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: Subtle problems with "info sharedlibrary" on MS-Windows
Date: Thu, 08 Apr 2021 10:06:54 +0300	[thread overview]
Message-ID: <83czv59rw1.fsf@gnu.org> (raw)
In-Reply-To: <f851cfb1-bf63-d43b-5016-98119c25d777@polymtl.ca> (message from Simon Marchi on Wed, 7 Apr 2021 17:18:08 -0400)

> Cc: gdb-patches@sourceware.org
> From: Simon Marchi <simon.marchi@polymtl.ca>
> Date: Wed, 7 Apr 2021 17:18:08 -0400
> 
> > OK to commit to master (with a suitable ChangeLog entry)?
> 
> The patch LGTM, see minor comments below.

Thanks for your prompt review (and for the other help in investigating
this tricky problem).

> According to our style guideline, we would use
> 
>   dll_name != nullptr

Does this also mean the GDB style prefers, e.g.,

    if (load_addr == nullptr)

to

    if (!load_addr)

?  Because you didn't comment on those lines, only on those where the
value is tested for NOT being null.

> > +      if (!(load_addr && mi.lpBaseOfDll != load_addr))
> 
> Perhaps matter of personal preference, but I would understand it better
> (less mental steps) as
> 
>     if (!load_addr || mi.lpBaseOfDll == load_addr)

I feel the other way around, but maybe I'm the odd one out here.
Pedro, Joel: what say you?

In any case, I guess I could add a comment there explaining the logic
in plain English, so everyone would understand the intent.

  reply	other threads:[~2021-04-08  7:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 12:36 Eli Zaretskii via Gdb-patches
2021-03-10 16:30 ` Hannes Domani via Gdb-patches
2021-03-10 16:51   ` Eli Zaretskii via Gdb-patches
2021-03-10 17:35     ` Hannes Domani via Gdb-patches
2021-04-05 17:51       ` Eli Zaretskii via Gdb-patches
2021-04-06 13:16         ` Eli Zaretskii via Gdb-patches
2021-04-07 21:18           ` Simon Marchi via Gdb-patches
2021-04-08  7:06             ` Eli Zaretskii via Gdb-patches [this message]
2021-04-08 13:57               ` Simon Marchi via Gdb-patches
2021-04-10  8:46                 ` Eli Zaretskii via Gdb-patches
2021-04-10 15:03           ` Tom Tromey
2021-04-10 18:07             ` Eli Zaretskii via Gdb-patches
2021-04-10 22:56               ` Simon Marchi via Gdb-patches
2021-04-10 23:11                 ` Simon Marchi via Gdb-patches
2021-04-11  7:10                 ` Eli Zaretskii via Gdb-patches
2021-04-11 12:27                   ` Simon Marchi via Gdb-patches
2021-04-11 18:43                     ` Eli Zaretskii via Gdb-patches
2021-04-12 19:03                       ` Tom Tromey

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=83czv59rw1.fsf@gnu.org \
    --to=gdb-patches@sourceware.org \
    --cc=eliz@gnu.org \
    --cc=simon.marchi@polymtl.ca \
    /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