Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Use SYMBOL_SET_NAMES in hpread
Date: Tue, 17 Feb 2004 01:42:00 -0000	[thread overview]
Message-ID: <20040217014218.GA5571@nevyn.them.org> (raw)
In-Reply-To: <20040217013517.0AE2F4B104@berman.michael-chastain.com>

On Mon, Feb 16, 2004 at 08:35:17PM -0500, Michael Chastain wrote:
> Alas, this patch didn't work.  Here are some of the regressions:
> 
> (gdb) break StringTest<wchar_t>::testFunction^M
> Internal: global symbol `StringTest<wchar_t>::testFunction(void)' found
> in /house/chastain/gdb/s1/gdb/testsuite/gdb.cp/bs15503.cc psymtab but
> not in symtab.^M  StringTest<wchar_t>::testFunction(void) may be an
> inlined function, or may be a template function^M
> (if a template, try specifying an instantiation:
> StringTest<wchar_t>::testFunction(void)<type>).^M
> (gdb) FAIL: gdb.cp/bs15503.exp: break StringTest<wchar_t>::testFunction
> 
> print &'dm_type_char_star'^M
> $2 = (<text variable, no debug info> *) 0x3648
> <dm_type_char_star__FPc>^M
> (gdb) FAIL: gdb.cp/cplusfuncs.exp: detect dm_type_char_star
> 
> ===
> 
> 2004-02-16  Daniel Jacobowitz  <drow@mvista.com>
> 
> 	* hpread.c (hpread_process_one_debug_symbol): Use SYMBOL_SET_NAMES
> 	and rely on the demangler.

Thanks.  Back to the drawing board on that one; I'll think about it...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-02-17  1:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17  1:35 Michael Elizabeth Chastain
2004-02-17  1:42 ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-16 22:04 Michael Elizabeth Chastain
2004-02-16 22:11 ` Elena Zannoni
2004-02-16 21:40 Michael Elizabeth Chastain
2004-02-16 21:51 ` Elena Zannoni
2004-02-16 21:21 Daniel Jacobowitz
2004-02-16 21:27 ` Daniel Jacobowitz

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=20040217014218.GA5571@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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