[M3devel] gdb on Darwin

[jay.krell at cornell.edu]

Wait a sec actually the problem might be larger here. Apple has its  
own object and executable format. I think its  own static linker. I  
think a very old fork of gas. We don't care particularly about  
'binutils' but it apparently intersects with gdb in bfd. There is  
investigation to be done but it wouldn't surprise me if this is a  
large permanent fork.

  - Jay (phone)

On Jul 17, 2009, at 4:27 PM, Jay K <jay.krell at cornell.edu> wrote:

> Apple doesn't push up all its changes, I think because they think/ 
> know they wouldn't all be accepted.
> But granted, actually just supporting a target, should be acceptable.
> Problems may be more like language changes for Mac source compat,  
> though I'd think with flags to turn them off/on, they'd be ok, but  
> that's another point.
>
> The lag does seem severe here though.
> I guess wait for the gdb 7.0 release and then reevaluate?
> In the meantime, no m3gdb for I386_DARWIN, AMD64_DARWIN.
> I haven't tried PPC_DARWIN yet.
>
> I agree the forking is unfortunate.
> Even if it is temporary, it seems to go too long.
>
>  - Jay
>
> > From: hosking at cs.purdue.edu
> > To: jay.krell at cornell.edu
> > Date: Fri, 17 Jul 2009 09:50:36 -0400
> > CC: m3devel at elegosoft.com
> > Subject: Re: [M3devel] gdb on Darwin
> >
> > Let's avoid pandering to Apple's forks. Better to upgrade to FSF
> > sources that (eventually) should catch up.
> >
> > Sent from my iPhone
> >
> > On Jul 17, 2009, at 8:46 AM, Jay K <jay.krell at cornell.edu> wrote:
> >
> > > Even current FSF gdb 6.8 doesn't built on Darwin/x86 or Darwin/ 
> AMD64.
> > > AMD64 gives and error that BFD is not supported.
> > > x86 skips the critical gdb directory because it isn't supported.
> > >
> > > If we want this to work, we should probably the importing Apple's
> > > fork?
> > > Like I did for ARM_DARWIN m3cc?
> > >
> > > - Jay
> > >
> > >
> > >