Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>
Cc: Svante Signell <svante.signell@gmail.com>,
	Andreas Schwab <schwab@linux-m68k.org>,
	gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH] Please define thread_info as struct thread_info (and other stuff)
Date: Thu, 20 Dec 2018 23:26:00 -0000	[thread overview]
Message-ID: <69b7d5f5ddfd13b33f62ff58e643af40@simark.ca> (raw)
In-Reply-To: <878t0j4ykk.fsf@tromey.com>

On 2018-12-20 17:34, Tom Tromey wrote:
>>>>>> "Svante" == Svante Signell <svante.signell@gmail.com> writes:
> 
> Svante> Seems like nothing is happening so far. Did you expect me to
> Svante> take action on this issue? Or is this a low-prio problem for
> Svante> you, Hurd being a second class citizen?
> 
> It's not so much second-class as that the usual way gdb development
> works is that ports need maintainers, and the current contributors are
> pretty busy and/or have other interests.

That's an important point.  For example, the Freebsd port is in pretty 
good shape, because somebody (thanks John) uses it daily and is able to 
report quickly any breakage to us non-Freebsd users.

I have tried earlier to give it a shot and build GDB using the image 
available here:

   https://www.gnu.org/software/hurd/hurd/running/qemu.html

but couldn't get very far (apt-get install wouldn't work).  Or at least, 
is there an easy way to get a cross-compiling environment for 
Debian/Hurd, let's say on Debian/Linux stable?

> I took a quick look at it and one question I have is whether
> nm-i386gnu.h really needs to include any of the headers it does.  
> defs.h
> already includes unistd.h, and regcache.h should probably not be 
> needed;
> and removing the mach includes would at least reduce the number of 
> spots
> needing the "struct".  Could you try removing these lines?
> 
> Also I happened to notice that file declares gnu_target_pid_to_str --
> but I didn't see a definition.  So perhaps that could be removed as
> well.

And to answer Svante's question about "what to do next", I think the 
intention long term was to put all of gdb in its own namespace, 
initially for fixing some gnulib clashes.  That's what triggered Pedro 
to do some C++ improvements (including wild matching).  For more 
details, see this, around the 15:00 mark:

https://slideslive.com/38902352/gdb-c-conversion-dogfooding-c

Looks like the prototype he did is on this branch:

https://github.com/palves/gdb/commits/palves/cxx-gdb-namespace

If this would fix the Hurd case, then maybe we can go with this.  Pedro, 
do you think we would be ready for such a move?  I would prefer to do 
that than to re-add a ton of "struct" keywords.

Simon


  reply	other threads:[~2018-12-20 23:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-15 19:36 Svante Signell
2018-12-15 22:48 ` Tom Tromey
2018-12-15 23:01   ` Svante Signell
2018-12-16  4:31     ` Simon Marchi
2018-12-16  5:14       ` Svante Signell
2018-12-16  6:02         ` Simon Marchi
2018-12-16 16:22         ` Tom Tromey
2018-12-16  9:20 ` Andreas Schwab
2018-12-16 19:08   ` Svante Signell
2018-12-16 23:10     ` Tom Tromey
2018-12-17 20:51       ` Svante Signell
2018-12-17 21:41         ` John Baldwin
2019-02-14 15:16           ` Thomas Schwinge
2018-12-20 13:31         ` Svante Signell
2018-12-20 22:34           ` Tom Tromey
2018-12-20 23:26             ` Simon Marchi [this message]
2018-12-24 21:51             ` Tom Tromey
2019-01-12 18:37               ` Svante Signell
2019-01-12 20:50                 ` 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=69b7d5f5ddfd13b33f62ff58e643af40@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=schwab@linux-m68k.org \
    --cc=svante.signell@gmail.com \
    --cc=tom@tromey.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