Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@ACT-Europe.FR>
To: gdb-patches@sources.redhat.com
Subject: [RFC] Uninitialized section index internal error on Tru64 5.1
Date: Fri, 12 Apr 2002 03:19:00 -0000	[thread overview]
Message-ID: <20020412121941.E16134@act-europe.fr> (raw)

This follows up on a discussion started over a year ago... Lack of time
prevented me from persuing this issue. Hopefully we can make progress
quickly. The last message on this topic was sent by me, and contains
a full description of what I believe is the source of the problem:

    http://sources.redhat.com/ml/gdb-patches/2001-11/msg00296.html

The following patch fixes many regressions in the testsuite:
    Summary 1       2
    FAIL    1644    792
    PASS    4388    6990
    XFAIL   59      149
    XPASS   1       3

I compiled on Tru64 5.1A, using GCC.

This patch is not meant to be integrated as is, this is more a first
rough fix presented so that we can discuss more precisely which
direction to take in order to complete the work.

In particular, should the "if section-is-uninitialized then discard"
bits be always there regardless of the target? Or should we put in place
some configure test in order to execute this test only on targets were
this is needed (alpha-osf is the only one that I know of).

There is also the get_section_index function that I quickly threw in. I
suppose it should be defined in a  .h file, and implemented somewhere
else than in mdebugread.c.

Cheers,
-- 
Joel


             reply	other threads:[~2002-04-12 10:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12  3:19 Joel Brobecker [this message]
2002-04-12  3:22 ` Joel Brobecker
2002-04-14 15:39 ` Elena Zannoni
2002-04-16 10:40   ` Joel Brobecker
2002-04-19  9:15     ` Elena Zannoni
2002-04-22  3:21       ` 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=20020412121941.E16134@act-europe.fr \
    --to=brobecker@act-europe.fr \
    --cc=gdb-patches@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