Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [NEWS/RFA] document hppa64-hpux support status
Date: Wed, 24 Oct 2007 21:23:00 -0000	[thread overview]
Message-ID: <20071024210952.GK11797@adacore.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 532 bytes --]

Hello,

Here is a patch against NEWS to document the status of hppa64-hpux.
I wasn't sure how to document this, since gdb-6.7 is also affected.
Rather than burying this in the gdb-6.7 section, I elected to put
it in the "since gdb-6.7" section, where people are more likely
to read it. I've added a note explicitly confirming that gdb-6.7
is also broken.

2007-10-24  Joel Brobecker  <brobecker@adacore.com>

        * NEWS: Document status of hppa64-hpux support.

I suggest this for the HEAD and 6.7 branch. Is that OK?

-- 
Joel

[-- Attachment #2: NEWS.diff --]
[-- Type: text/plain, Size: 706 bytes --]

Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.244
diff -u -p -r1.244 NEWS
--- NEWS	21 Oct 2007 10:27:49 -0000	1.244
+++ NEWS	24 Oct 2007 21:09:23 -0000
@@ -18,6 +18,11 @@ and in inlined functions.
 * The GDB remote stub, gdbserver, now supports the AltiVec and SPE
 registers on PowerPC targets.
 
+* hppa*64*-*-hpux11* target broken
+  The debugger is unable to start a program and fails with the following
+  error: "Error trying to get information about dynamic linker".
+  The gdb-6.7 release is also affected.
+
 *** Changes in GDB 6.7
 
 * Resolved 101 resource leaks, null pointer dereferences, etc. in gdb, 

             reply	other threads:[~2007-10-24 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 21:23 Joel Brobecker [this message]
2007-10-25  5:55 ` Eli Zaretskii
2007-10-25  7:18   ` Joel Brobecker

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=20071024210952.GK11797@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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