Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tom@tromey.com>, Xavier Roirand <roirand@adacore.com>,
	       gdb-patches@sourceware.org
Subject: Re: [RFA 2/5] Darwin: Handle unrelocated dyld.
Date: Wed, 19 Sep 2018 14:16:00 -0000	[thread overview]
Message-ID: <87d657aa82a5a114995d8035c4f2f125@polymtl.ca> (raw)
In-Reply-To: <20180919134057.GN19172@adacore.com>

On 2018-09-19 09:40, Joel Brobecker wrote:
> That makes me realize (again) that, for MacOS X, we should be more
> proactive at specificying which version a patch we are submitting
> was tested on, and some information about which versions of MacOS X
> a given patch helps. A fair amount of work that Tristan did once
> the initial port was created was to adapt it to subsequent versions
> of Darwin. Nearly every new version of Darwin introduced its new
> set of changes requiring additional adaptations.

Given the low amount of resources we have to work on GDB for macOS and 
the fact that it's difficult for one person to test on different 
versions of macOS (you would need multiple Mac computers, AFAIK), I 
suggest that we only aim at supporting the last two released versions of 
macOS.  I say two, because there will always be an overlap after a new 
version is released, where some people use the new version and others 
have not upgraded yet.

If some people use older versions of macOS and want to contribute 
patches and help testing, that's fine too, but if everybody contributing 
is on latest or latest-1, we can't realistically ensure it works on 
previous versions.

That said, I agree that it would be very helpful if commit messages and 
comments in the code mentioned the version of macOS that was used at the 
time that commit message or comment was written.

Simon


  reply	other threads:[~2018-09-19 14:16 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 10:11 [RFA 0/5] Fix some bugs on macOS Xavier Roirand
2018-08-22 10:11 ` [RFA 2/5] Darwin: Handle unrelocated dyld Xavier Roirand
2018-08-22 13:55   ` Simon Marchi
2018-09-18 21:22     ` Tom Tromey
2018-09-19 13:41       ` Joel Brobecker
2018-09-19 14:16         ` Simon Marchi [this message]
2018-09-19 14:28           ` Joel Brobecker
2018-09-19 14:36         ` Tom Tromey
2018-09-19 14:44           ` Simon Marchi
2018-09-19 15:32             ` Joel Brobecker
2018-09-19 19:15             ` Tom Tromey
2018-09-19 19:50               ` Simon Marchi
2018-09-28 13:31               ` Xavier Roirand
2018-09-28 17:22                 ` Tom Tromey
2018-08-22 13:59   ` Simon Marchi
2018-09-18 21:23     ` Tom Tromey
2018-08-22 10:11 ` [RFA 1/5] Darwin: fix bad loop incrementation Xavier Roirand
2018-08-22 13:14   ` Simon Marchi
2018-08-23 15:21     ` Simon Marchi
2018-08-22 10:11 ` [RFA 3/5] Darwin: set startup-with-shell to off on Sierra and later Xavier Roirand
2018-08-22 14:20   ` Simon Marchi
2018-08-22 14:37     ` Pedro Alves
2018-09-03 13:23     ` Xavier Roirand
2018-09-17 19:31   ` Tom Tromey
2018-08-22 10:11 ` [RFA 4/5] Darwin: fix thread ptid started by fork_inferior Xavier Roirand
2018-08-22 14:30   ` Simon Marchi
2018-08-22 16:10   ` Pedro Alves
2018-08-22 18:14     ` Simon Marchi
2018-08-22 10:11 ` [RFA 5/5] Darwin: fix SIGTRAP when debugging Xavier Roirand
2018-08-22 14:34   ` Simon Marchi
2018-09-17 20:57 ` [RFA 0/5] Fix some bugs on macOS Tom Tromey
2018-09-17 21:25   ` Joel Brobecker
2018-09-17 23: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=87d657aa82a5a114995d8035c4f2f125@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=roirand@adacore.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