Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Time for a HP/PA hackathon?
Date: Sat, 14 Feb 2004 15:54:00 -0000	[thread overview]
Message-ID: <402E44AF.2030801@gnu.org> (raw)
In-Reply-To: <20040214031427.AA14B4B104@berman.michael-chastain.com>

> What happens if -D_LARGEFILE64_SOURCE is added?  (Not sure of the 
>> correct way to do that in BFD though).
> 
> 
> "./gdb ./gdb" ; "break main" ; "run" works.
> 
> And it works with gdb built with gcc 3.3.2, ansi c B11.11,
> and aC++ A.03.45.

I've checked in a (hopeful) fix.

> I do think you're opening up a big can of worms shortly before
> the 6.1 branch though.

The 64-bit off_t, enabling the TUI, the HP/UX frame update, or the BFD 
file I/O rewrite?  Of these, it's the TUI that scares me me the most. 
History shows that only after we've released do we learn about the 
breakage on the non- mainstream systems.

I do wonder if the next binutils branch should be held off until after 
GDB's been released - so that it can learn from GDB's mistakes :-)

Andrew

PS: You haven't seen my post 6.1 branch backlog :-)



  reply	other threads:[~2004-02-14 15:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-14  3:14 Michael Elizabeth Chastain
2004-02-14 15:54 ` Andrew Cagney [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-14 20:00 Michael Elizabeth Chastain
2004-02-15  1:20 ` Daniel Jacobowitz
2004-02-13 22:39 Michael Elizabeth Chastain
2004-02-14  2:01 ` Andrew Cagney
2004-02-13 18:13 Michael Elizabeth Chastain
2004-02-13 18:32 ` Elena Zannoni
2004-02-13 18:48   ` Andrew Cagney
2004-02-13 16:29 Michael Elizabeth Chastain
2004-02-13 16:54 ` Andrew Cagney
2004-02-11 17:05 Andrew Cagney

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=402E44AF.2030801@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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