Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Bhushan Attarde" <Bhushan.Attarde@kpitcummins.com>
To: "Daniel Jacobowitz" <drow@false.org>, 	<gdb@sourceware.org>
Subject: RE: error message : I'm sorry, Dave, I can't do that.Symbolformat 'elf32-xc16x' unknown.
Date: Wed, 26 Sep 2007 07:36:00 -0000	[thread overview]
Message-ID: <7B5265FF85A78C4BB9DAD0EE699C476002B730EC@sohm.kpit.com> (raw)



>>Is it in libbfd.a?  What does gdb/config.log say about it?

I checked libbfd.a by  
$ nm libbfd.a | grep bfd_get_elf_phdr_upper_bound
	.....
	.....
elf.o:
00000000 b .bss
00000000 d .data
00000000 r .rdata
00000000 t .text
	....
	....
00009231 T _bfd_get_elf_phdr_upper_bound
		


Then in gdb/config.log I found many undefined references & failed
programs.
Please find attached config.log file to have closer look.      
	

--Bhushan Attarde



-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org] 
Sent: Monday, September 24, 2007 4:38 PM
To: Bhushan Attarde
Cc: gdb@sourceware.org
Subject: Re: error message : I'm sorry, Dave, I can't do
that.Symbolformat 'elf32-xc16x' unknown.

On Mon, Sep 24, 2007 at 03:37:50PM +0530, Bhushan Attarde wrote:
> but I didn't find this function in any of the processor specific file
so
> I am little confused where to add this function to work for our
target.

Is it in libbfd.a?  What does gdb/config.log say about it?

-- 
Daniel Jacobowitz
CodeSourcery


             reply	other threads:[~2007-09-26  6:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26  7:36 Bhushan Attarde [this message]
     [not found] <7B5265FF85A78C4BB9DAD0EE699C476002B73136@sohm.kpit.com>
2007-09-26 21:28 ` Daniel Jacobowitz
2007-09-27 12:44   ` error message : I'm sorry, Dave, I can't do that.Symbolformat'elf32-xc16x' unknown Bhushan Attarde
2007-09-27 13:46     ` 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=7B5265FF85A78C4BB9DAD0EE699C476002B730EC@sohm.kpit.com \
    --to=bhushan.attarde@kpitcummins.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /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