Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Steven Johnson <sjohnson@sakuraindustries.com>
Cc: gdb-patches@sourceware.org
Subject: Re: psymtab not in symtab warning patch
Date: Tue, 13 Jun 2006 23:13:00 -0000	[thread overview]
Message-ID: <vt2slm86459.fsf@theseus.home.> (raw)
In-Reply-To: <448BB966.3050200@sakuraindustries.com> (Steven Johnson's message of "Sun, 11 Jun 2006 17:34:14 +1100")


Steven Johnson <sjohnson@sakuraindustries.com> writes:
> Please consider the attached patch.
>
> It allows the "PC 0x??? in psymtab but not in symtab" warning to be
> "toggled off".  The reason for this, is for whatever reason I get it
> heaps with my PPC Assembler code.  There doesn't appear to be any
> obvious incantation to control it or prevent it when building the asm
> files, so i've given up trying.  The attached patch retains the current
> behaviour, but if someone is being inundated by the warning, which
> happens when it occurs, they can turn it off, and at least continue
> debugging OK.
>
> Obviously finding out why it happens is far better, but i know nothing
> about dwarf debug information, or the psymtab or symtab stuff, so i'm
> not going to be productive in finding a better answer.

I'm happy to debug this, if you can get me an executable to work with.
Large is fine, just something you can share.

As far as the patch goes --- we probably want to use a complaint here;
see 'complaints.h', and see how they're used in dwarf2read.c.  That
will automatically limit the number of times you see the complaint,
the default being zero.


      reply	other threads:[~2006-06-13 23:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-11  6:34 Steven Johnson
2006-06-13 23:13 ` Jim Blandy [this message]

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=vt2slm86459.fsf@theseus.home. \
    --to=jimb@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sjohnson@sakuraindustries.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