Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: <gdb@sourceware.org>
Subject: Re: GDB w/ Mac OS cores: "no core file handler recognizes format"
Date: Fri, 31 Jan 2014 20:55:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1401312050050.30733@digraph.polyomino.org.uk> (raw)
In-Reply-To: <52EBE906.9010701@earthlink.net>

On Fri, 31 Jan 2014, Stan Shebs wrote:

> No, Apple had a blanket assignment to the FSF for all of their GNU work.

But did the code only get assigned by that assignment when it was actually 
submitted to the FSF by Apple, rather than simply by being created and 
published?

My understanding for GCC was that anything on the 4.0-based branch in the 
FSF repository was assigned by virtue of being committed to that 
repository, but the 4.2-based sources weren't (hence, in particular, 
implementation of blocks for GCC would need either something to be done 
about assignment of the 4.2-based code from Apple, or a complete 
reimplementation; cf <http://gcc.gnu.org/ml/gcc/2013-11/msg00039.html>) - 
and that it was generically the case for such assignments that changes 
became assigned at the point where they were submitted by or with the 
consent of the previous owner.

-- 
Joseph S. Myers
joseph@codesourcery.com


  parent reply	other threads:[~2014-01-31 20:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1391120555.28742.307.camel@pdsdesk>
2014-01-31  2:09 ` Joel Brobecker
2014-01-31  3:20   ` Klee Dienes
2014-01-31  7:58     ` Matt Rice
2014-01-31 13:34       ` Klee Dienes
2014-01-31 18:18       ` Stan Shebs
2014-01-31 18:41         ` Paul Smith
2014-01-31 20:55         ` Joseph S. Myers [this message]
2014-01-31 21:10           ` Matt Rice
2014-01-31  9:50   ` Tristan Gingold

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=Pine.LNX.4.64.1401312050050.30733@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=gdb@sourceware.org \
    --cc=stanshebs@earthlink.net \
    /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