public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Jungsoo Sohn <amamos@dallext.hansung.ac.kr>, gdb@sources.redhat.com
Subject: Re: do you know this error..
Date: Tue, 13 May 2003 16:13:00 -0000	[thread overview]
Message-ID: <20030513161250.GA26624@nevyn.them.org> (raw)
In-Reply-To: <3EC11803.3070707@eagercon.com>

On Tue, May 13, 2003 at 09:06:27AM -0700, Michael Eager wrote:
> Jungsoo Sohn wrote:
> > host machine : i386, redhat 7.3 , gdb: 5.3
> > target machine : mips, hardhat-2.4.18
> > ./configure --host=i386-redhat-linux-gun --target=mipsel-linux-elf

Also, mipsel-linux-elf is almost certainly not what you want.  Use
mipsel-linux instead.

> > 
> > error occurred:
> > (gdb) add-symbol-file dvr.o 0xc000d060\
> >  -s .reginfo 0xc000d350\
> >  -s .rodata 0xc000d370\
> >  -s .data 0xc000d620\
> >  -s .bss 0xc000d670
> > add symbol table from file "dvr.o" at
> >  .text_addr = 0xc000d060
> >  .reginfo_addr = 0xc000d350
> >  .rodata_addr = 0xc000d370
> >  .data_addr = 0xc000d620
> >  .bss_addr = 0xc000d670
> > (gdb) b dvr_rw_dev
> > Breakpoint 3 at 0xc000d30c
> > (gdb) c 
> > (gdb) c
> > write!
> > 
> > Program received signal SIGTRAP, Trace/breakpoint trap.
> > 0xffffffffc000d30c in ?? ()
> > (gdb) 
> > 
> > '0xffffffffc000d30c in ?? ()' what is this? what's problem? 
> 
> Looks like the address is formatted as a 64-bit value.  Ignore
> the top 32 bits.
> 
> Did you compile with -g?
> 
> -- 
> Michael Eager	 Eager Consulting     eager@eagercon.com
> 1960 Park Blvd., Palo Alto, CA 94306  650-325-8077
> 
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

      reply	other threads:[~2003-05-13 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12  2:41 Jungsoo Sohn
2003-05-13 16:06 ` Michael Eager
2003-05-13 16:13   ` Daniel Jacobowitz [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=20030513161250.GA26624@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=amamos@dallext.hansung.ac.kr \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).