public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Yigit Can <yigit.can@karel.com.tr>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Debug problem?
Date: Mon, 24 Mar 2003 15:46:12 +0200	[thread overview]
Message-ID: <001901c2f20b$bbc8db60$3002a8c0@yigitcan> (raw)

writing 

=> target remote 192.168.2.52:2001
0x00000100 in ?? ()

it connects and i wrote

=> continue

=> press CTRL+C

=>l
1     {standard input}: No such file or directory.
       in {standard input}

I can not see the source code
but i can see register values with
=> info registers
or
=>print  $pc



I am running ppc_8xx-gdb in /opt/eldk/ppc_8xx/usr/src/ppcboot-1.2.1 where i
built ppcboot.

Thanks



----- Original Message -----
From: "Wolfgang Denk" <wd@denx.de>
To: "Yigit Can" <yigit.can@karel.com.tr>
Cc: <u-boot-users@lists.sourceforge.net>
Sent: Monday, March 24, 2003 10:05 AM
Subject: Re: [U-Boot-Users] Debug problem?


In message <002401c2f1cc$47ede2b0$3002a8c0@yigitcan> you wrote:
> I am using Denx ELDK
>
> For debug of ppcboot:
> The Commands I wrote  and responses are :
>
> #ppc_8xx-gdb ppcboot

Which is your current directory when you enter this comand? Where did you
build the ppcboot binary?

> =>dir /opt/eldk/ppc_8xx/usr/src/ppcboot-1.2.1
> directory searched ...

Why are you entering this command? If you built thePPCBoot binary  in
this   directory,   it  should  not  be  necessary,  since  GDB  will
automatically use $cdir:$cwd as it's directory search. If  you  built
PPCBoot  in  a  different directory and use this as current directory
the command should not be necessary either for the same reason.

> =>l
>
> 1     {standard input}: No such file or directory.
>        in {standard input}

You are not running the program yet. No source file is being executed
yet. You cannot show other information like registers, either:

(gdb) info registers
The program has no registers now.
(gdb) print $pc
No registers.


> what can i do with this error
> I can see -g option in compilation logs

Start the program (by attaching to a remote target  and  "continue"),
and everything will be well :-)


Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
He'd been wrong, there _was_ a light at the end of the tunnel, and it
was a flamethrower.                         - Terry Pratchett, _Mort_


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users

             reply	other threads:[~2003-03-24 13:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 13:46 Yigit Can [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-24 10:00 [U-Boot-Users] Debug problem? Yigit Can
2003-03-21 11:18 [U-Boot-Users] bdigdb problem? Yigit Can
2003-03-24  6:12 ` [U-Boot-Users] Debug problem? Yigit Can
2003-03-24  8:05   ` Wolfgang Denk

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='001901c2f20b$bbc8db60$3002a8c0@yigitcan' \
    --to=yigit.can@karel.com.tr \
    --cc=u-boot@lists.denx.de \
    /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