Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: mrcompiler@mrcompiler.com
To: gdb@sources.redhat.com
Subject: Multi-Arch symbol read warning message
Date: Thu, 20 Feb 2003 22:30:00 -0000	[thread overview]
Message-ID: <20030220222419.21758.qmail@admin1.cvtt.net> (raw)

I am building a multi-arch version of GDB for handling ELF format core files 
for the ARM and PowerPC processors running on vxWorks. In order to get 
everything to build I combined the information from 
config/powerpc/vxworks.mt and config/arm/embed.mt and made the appropriate 
changes necessary to compile with GDB_MULTI_ARCH=GDB_MULTI_ARCH_PURE. 

The top level config is: 

./configure --target=arm-vxworks --enable-targets=strongarm-coff, 
powerpc-elf, strongarm-elf 

I was not able to get it working with --enable-targets=all since bfd 
couldn't resolve the appropriate architecture, but that's a secondary issue. 

I had to set the target to arm-vxworks instead of powerpc-vxworks in order 
to get the appropriate remote stuff to link. Otherwise it was off to hack 
the configure.in and related files which seemed like an extraordinary amount 
of unecessary work. 

Everything seems to work fine except for one, probably cosmetic, issue. When 
I load a PowerPC symbol-file I get the warning 

"unknown symbol descriptor `;`" which doesn't appear if I build a "pure" 
powerpc-vxworks target. 

Using gdb on gdb it seems like this is related somehow to the native target. 

I have two questions: 

1) does this indicate a significant issue? 

2) If not is there a solution other than suppressing the warning in 
dbxread.c? 

A prompt response would be appreciated greatly as my boss is breathing down 
my neck to make this available. I'd have to have my team debugging with a 
faulty debugger. 

Thanks,
Gene 


             reply	other threads:[~2003-02-20 22:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 22:30 mrcompiler [this message]
2003-02-21  4:23 ` Jim Blandy
2003-02-22  3:23   ` mrcompiler
2003-02-22 16:20     ` Daniel Jacobowitz
2003-02-22  3:46 ` Andrew Cagney
2003-02-22 17:32   ` mrcompiler

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=20030220222419.21758.qmail@admin1.cvtt.net \
    --to=mrcompiler@mrcompiler.com \
    --cc=gdb@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