Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>, gdb@sourceware.org
Cc: Marco van de Voort <marcov@stack.nl>
Subject: Re: errors in GDB reading symbols
Date: Tue, 04 Aug 2009 14:47:00 -0000	[thread overview]
Message-ID: <20090804144714.GA31300@caradoc.them.org> (raw)
In-Reply-To: <20090804144634.GA30893@caradoc.them.org>

Really CC'd this time, sorry.

On Tue, Aug 04, 2009 at 10:46:34AM -0400, Daniel Jacobowitz wrote:
> On Tue, Aug 04, 2009 at 08:33:28AM -0600, Tom Tromey wrote:
> > I looked into this yesterday.
> > 
> > Removing this doesn't shave much time off the build -- 5 seconds on my
> > machine.  Still, it would probably be good to do.  While doing this, I
> > did discover we have duplicate objects in libgdb.a, oops.
> > 
> > I think the Free Pascal folks already know about this problem:
> > 
> > http://www.mail-archive.com/fpc-devel@lists.freepascal.org/msg13661.html
> 
> Sad to see so much stale information about GDB; at least it has one
> defender on that list, though (thanks Jonas).
> 
> Forwarding with permission, from Marco van de Voort (CC'd; Marco, this
> is an open list, so feel free to reply and it won't bounce):
> 
> > >Unfortunately, there's an IDE (Free Pascal?) that uses it.  I don't
> > >know of other uses.
> 
> > The (libgdb usage) was copied from RHIDE.
> 
> > >I'm still in favor of being rid of it; but we should warn them
> > >directly.
> 
> > Note that one of the main reasons is the lack of some systems not
> > supporting multitasking. Not having a linkable version afaik will make
> > using GDB in an IDE for such purposes difficult to impossible.
> 
> > Typically that means Dos/DJGPP, but there could some embedded uses
> > here and there also.
> 
> If we don't gain anything from the removal of libgdb.a, DJGPP support
> for the Free Pascal IDE is at least some reason to keep it.  Not a
> great one, IMO, but better than none...
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery
> 

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-08-04 14:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-01 21:38 kceiwH
2009-08-02 23:45 ` kceiwH
2009-08-03 16:53 ` Tom Tromey
2009-08-03 17:01   ` Daniel Jacobowitz
2009-08-03 20:47     ` Baurzhan Ismagulov
2009-08-04 14:33     ` Tom Tromey
2009-08-04 14:46       ` Daniel Jacobowitz
2009-08-04 14:47         ` Daniel Jacobowitz [this message]
2009-08-04 14:52       ` Jonas Maebe
2009-08-04 14:55         ` Daniel Jacobowitz
2009-08-06 17:09         ` Tom Tromey
2009-08-06 21:00           ` Jonas Maebe
2009-08-07 16:24             ` Daniel Jacobowitz
2009-08-07 20:48 Marco van de Voort
2009-08-11 21:00 ` Tom Tromey
2009-08-12  0:56   ` Paul Pluzhnikov
2009-08-21 17:33     ` 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=20090804144714.GA31300@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=marcov@stack.nl \
    --cc=tromey@redhat.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