Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Joel Brobecker <brobecker@ACT-Europe.FR>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Uninitialized section index internal error on Tru64 5.1
Date: Sun, 14 Apr 2002 15:39:00 -0000	[thread overview]
Message-ID: <15546.1263.304306.933281@localhost.redhat.com> (raw)
In-Reply-To: <20020412121941.E16134@act-europe.fr>

Joel Brobecker writes:
 > 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.
 > 

I don't mind this patch as is actually.

 > 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).
 > 

Yeah, I see your point. It seems like the real problem is that a
storage class is assigned w/o a corresponding section being
there. Does the section ever exist, does it get optimized out at some
point? Your comments explain pretty well what's going on, so I am inclined
to leave the "continue's" in.

 > 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.
 > 

I would suggest symfile.c and symfile.h.

Elena


 > Cheers,
 > -- 
 > Joel


  parent reply	other threads:[~2002-04-14 22:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12  3:19 Joel Brobecker
2002-04-12  3:22 ` Joel Brobecker
2002-04-14 15:39 ` Elena Zannoni [this message]
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=15546.1263.304306.933281@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=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