public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Lancelot SIX <lsix@lancelotsix.com>
Cc: Tom Tromey <tromey@adacore.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH] Add gdb.free_objfile event registry
Date: Mon, 18 Jul 2022 11:25:02 -0600	[thread overview]
Message-ID: <877d4al4ep.fsf@tromey.com> (raw)
In-Reply-To: <20220620183612.px4ct47mq36tyqfo@ubuntu.lan> (Lancelot SIX's message of "Mon, 20 Jun 2022 18:36:32 +0000")

>> +   Copyright 2010-2022 Free Software Foundation, Inc.

Lancelot> Is the 2010 intentional?  It looks that this file is copied from
Lancelot> gdb.base/catch-load.c which is marked 2012-2022.

I changed it to just 2022.

>> +/* This is updated by the .exp file.  */
>> +char *libname = "catch-load-so.so";

Lancelot> To be "consistent" with other files which uses this pattern, shouldn't
Lancelot> the default libname reflect the test name? Something like
Lancelot> py-event-load-so.so I guess.  Later in the test you use
Lancelot> "py-events-shlib.so" as actual libname.

I updated this.

>> +clean_restart $testfile
>> +
>> +if {![runto_main]} {
>> +    return
>> +}
>> +
>> +if { [skip_python_tests] } { return }

Lancelot> I guess that this skip check can be moved above (together with the
Lancelot> skip_shlib_tests), so on target which skip python tests we do not bother
Lancelot> compiling the test program.  WDYT?

Unfortunately, skip_python_tests requires that gdb already be running.

I'm going to check in the updated patch now.

Tom

      reply	other threads:[~2022-07-18 17:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20 17:36 Tom Tromey
2022-06-20 18:21 ` Eli Zaretskii
2022-06-20 18:36 ` Lancelot SIX
2022-07-18 17:25   ` Tom Tromey [this message]

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=877d4al4ep.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lsix@lancelotsix.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 read-only IMAP folder(s) and NNTP newsgroup(s).