From: gdb@thewrittenword.com
To: gdb@sources.redhat.com
Subject: Re: GDB 5.1 on Tru64 UNIX 4.0D, 5.0, 5.1
Date: Mon, 26 Nov 2001 15:01:00 -0000 [thread overview]
Message-ID: <20011126170153.B28540@oolong.il.thewrittenword.com> (raw)
In-Reply-To: <20011126163601.A28540@oolong.il.thewrittenword.com>
On Mon, Nov 26, 2001 at 04:36:01PM -0600, gdb@thewrittenword.com wrote:
> On Mon, Nov 26, 2001 at 10:31:04PM +0200, Eli Zaretskii wrote:
> > > From: gdb@thewrittenword.com
> > > Date: Mon, 26 Nov 2001 13:48:26 -0600
> > > >
> > > > Search the file README for "alpha-dec-osf4", it's all there.
> > >
> > > Are you sure?
> > >
> > > $ cd gdb-5.1
> > > $ grep -i alpha gdb/README
> > > [no output]
> >
> > Yes, I'm sure:
> >
> > $ grep -i alpha gdb/README
> > alpha-dec-osf5.1
> > alpha-dec-osf4.0e
> >
> > Here's the entry in its entirety:
> >
> > alpha-dec-osf4.0e
> >
> > GDB 5.1 is known to have problems on this platform (encounters an
> > internal error in the symbol table reader).
>
> Oh well. Doesn't work for me.
To clarify, CC='cc -DUSE_LDR_ROUTINES' produced the same results on
Tru64 UNIX 5.1.
--
albert chin (china@thewrittenword.com)
WARNING: multiple messages have this Message-ID
From: gdb@thewrittenword.com
To: gdb@sources.redhat.com
Subject: Re: GDB 5.1 on Tru64 UNIX 4.0D, 5.0, 5.1
Date: Wed, 14 Nov 2001 18:23:00 -0000 [thread overview]
Message-ID: <20011126170153.B28540@oolong.il.thewrittenword.com> (raw)
Message-ID: <20011114182300.dje7aHqGOHInxYehkfsTS3jv19FRCw3imcBe9HOYrV4@z> (raw)
In-Reply-To: <20011126163601.A28540@oolong.il.thewrittenword.com>; from gdb@thewrittenword.com on Mon, Nov 26, 2001 at 04:36:01PM -0600
On Mon, Nov 26, 2001 at 04:36:01PM -0600, gdb@thewrittenword.com wrote:
> On Mon, Nov 26, 2001 at 10:31:04PM +0200, Eli Zaretskii wrote:
> > > From: gdb@thewrittenword.com
> > > Date: Mon, 26 Nov 2001 13:48:26 -0600
> > > >
> > > > Search the file README for "alpha-dec-osf4", it's all there.
> > >
> > > Are you sure?
> > >
> > > $ cd gdb-5.1
> > > $ grep -i alpha gdb/README
> > > [no output]
> >
> > Yes, I'm sure:
> >
> > $ grep -i alpha gdb/README
> > alpha-dec-osf5.1
> > alpha-dec-osf4.0e
> >
> > Here's the entry in its entirety:
> >
> > alpha-dec-osf4.0e
> >
> > GDB 5.1 is known to have problems on this platform (encounters an
> > internal error in the symbol table reader).
>
> Oh well. Doesn't work for me.
To clarify, CC='cc -DUSE_LDR_ROUTINES' produced the same results on
Tru64 UNIX 5.1.
--
albert chin (china@thewrittenword.com)
next prev parent reply other threads:[~2001-11-26 15:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-14 1:38 gdb
2001-11-16 5:53 ` Scott Snyder
2001-11-17 9:11 ` Joel Brobecker
2001-11-27 5:51 ` Joel Brobecker
2001-11-26 22:08 ` Scott Snyder
2001-11-26 8:45 ` gdb
2001-11-26 11:11 ` Eli Zaretskii
2001-11-14 8:04 ` Eli Zaretskii
2001-11-26 11:48 ` gdb
2001-11-14 12:16 ` gdb
2001-11-14 12:27 ` Eli Zaretskii
2001-11-14 16:07 ` gdb
2001-11-26 15:01 ` gdb [this message]
2001-11-14 18:23 ` gdb
2001-11-26 12:32 ` Eli Zaretskii
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=20011126170153.B28540@oolong.il.thewrittenword.com \
--to=gdb@thewrittenword.com \
--cc=gdb@sources.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