public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: "Chu, Josh" <josh.chu@retek.com>
Cc: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: Re: 64bit gdb for KAI/KCC compiler
Date: Fri, 28 Jun 2002 06:31:00 -0000	[thread overview]
Message-ID: <20020628133112.GB31848@nevyn.them.org> (raw)
In-Reply-To: <E6C33530C94CD311ABB20008C791D6C313E103F1@mspmail1.retek.int>

On Thu, Jun 27, 2002 at 05:36:03PM -0500, Chu, Josh wrote:
> Ok, so here's the deal : KAI released a patch for gdb 5.0 that will allow
> gdb to read the EDG-style mangled names.  I've attached the patch files that
> were to be applied to 5.0 (gdb.patch-5.0 and libiberty.patch-5.0).  I tried
> manually applying these modifications to the 5.2 source, and it builds.
> However, there are some definite problems because gdb will now core dump
> occasionally, not to mention the names are still mangled.
> I've included the patch files to 5.0 and my modifications to the files in
> 5.2 :
>  
> gdb/libiberty:
>     cplus-dem.c
>  
> gdb/gdb:
>     dwarf2read.c
>     hpread.c
>     stabsread.c
>     symfile.c

> After this is done, you can try to build and run.  (export CC='gcc -m64' and
> ./configure first)

What platform is this, Solaris?  Looks like it from the m64.

> I suppose this is a fairly vague question : but does anyone have a clue why
> the patches aren't working with 5.2?
> This would be a huge help for anyone who has a KAI compiler on a 64-bit
> system, as it would allow people to debug 64bit programs compiled with KCC.
> Or if someone who's familiar with the above-mentioned files could comment on
> the patched files and what could potentially be wrong with them, I would
> very much appreciate it.
> Thanks so much

I'm more curious why they worked with 5.0.  I imagine they had very
limited functionality, since there is a great deal more to do in C++
support than demangle names properly.

I skimmed the patches and nothing jumps out at me as immediately wrong
except for:
!       if ( !EDG_DEMANGLING && !is_edg_temporary_var(sym) )
!         add_symbol_to_list (sym, &local_symbols);

That should probably be || if you ever want to see a local static
variable in GDB.... also, you do not need to comment out
finish_cv_type.



-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2002-06-28 13:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-27 15:37 Chu, Josh
2002-06-28  6:31 ` Daniel Jacobowitz [this message]
2002-06-28  6:47 Chu, Josh

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=20020628133112.GB31848@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=josh.chu@retek.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).