Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stan@codesourcery.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Darwin/x86 port (v4 - part 1/4: machoread.c)
Date: Tue, 18 Nov 2008 17:20:00 -0000	[thread overview]
Message-ID: <49221AE9.5050600@codesourcery.com> (raw)
In-Reply-To: <7B1402FF-6CAB-4C6A-AAB5-81E062080FB5@adacore.com>

Tristan Gingold wrote:
>
> typedef struct oso_el
> {
Something about what this struct is for, please? And while you and I 
know that "oso" is short for "other source" and refers to the collection 
of debug info from .o files, it's new to everybody else. :-) (Getting 
function bounds set correctly is going to be loads of fun, ahem, I had 
to look at Apple's hairy code for this several months ago...)
> DEF_VEC_O(oso_el);
> static VEC(oso_el) *oso_vector;
The vector macros should follow the "space before paren" just as 
everybody else does, although I note that the doc in vec.h confuses 
things by not following the general rule.
> #define DSYM_SUFFIX ".dSYM/Contents/Resources/DWARF/"  
Again, need to say what dSYM files are, and maybe mention that the yucky 
wired-in string is guaranteed to have that form (or at least that we're 
doing the same thing as Apple's GDB).

In comments, we should prefer to say "Mach-O" rather than "macho" or 
"mach-o", since that is the proper name of the file format.

With these doc and formatting changes, machoread.c is OK to go into the 
trunk.

(Ideally we will migrate this file to the list of generic files, but we 
will need to check that it compiles on other hosts first.)

Stan


  reply	other threads:[~2008-11-18  1:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 18:33 Tristan Gingold
2008-11-18 17:20 ` Stan Shebs [this message]
2008-11-18 19:54   ` Daniel Jacobowitz
2008-11-18 21:46     ` Stan Shebs
2008-11-18 21:50       ` Daniel Jacobowitz
2008-11-19 21:21   ` Tristan Gingold
2008-11-26 16:30     ` Stan Shebs

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=49221AE9.5050600@codesourcery.com \
    --to=stan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gingold@adacore.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