Tools question

Tools question

[Jay Denebeim]

Given a kernel panic with a partial traceback (actually it's a jpg
taken with a digital camera of a screen), how would I identify the
line where the panic occured.

Basically I want something that tells me the offsets of a given line
of code.  I've used tools to do this on other operating systems, what
should I use on Linux?

Jay

-- 
* Jay Denebeim  Moderator       rec.arts.sf.tv.babylon5.moderated *
* newsgroup submission address: b5mod@deepthot.org                *
* moderator contact address:    b5mod-request@deepthot.org        *
* personal contact address:     denebeim@deepthot.org             *

Re: Tools question

[Jurriaan]

From: Jay Denebeim <denebeim@deepthot.org>
Date: Thu, Oct 30, 2003 at 10:40:42PM +0000
> Given a kernel panic with a partial traceback (actually it's a jpg
> taken with a digital camera of a screen), how would I identify the
> line where the panic occured.
> 
Oh, and next time, please use a working email address.

   ----- The following addresses had permanent fatal errors -----
<linuxkernel@deepthot.org>
    (reason: 550 Unrouteable address)

   ----- Transcript of session follows -----
... while talking to mail.deepthot.org.:
>>> DATA
<<< 550 Unrouteable address
550 5.1.1 <linuxkernel@deepthot.org>... User unknown
<<< 503 valid RCPT command must precede DATA

I'd have liked not to pollute linux-kernel with the answer, as I presume
it's already known by almost all people. So a private email would have
been my first choice.

Jurriaan
-- 
If it wasn't for C, we would be using BASI, PASAL and OBOL!
Debian (Unstable) GNU/Linux 2.6.0-test9-mm1 4276 bogomips 0.89 0.37

Tools question

[Christopher R. Johnson]

This is probably way too big a question to ask here, but I'm hoping
someone can help me.  I have inherited a gcc 2.95.3 cross development
tool chain, which has been working fine to build for my powerpc-linux
target machine.  I'm building the kernel and user programs fine.  I'm
beginning to find as I add things in that I'm missing libraries.  Today
its libresolv which I need for pump.  Some questions:

1. Do I really need to go back and build my own tool chain?  I've tried
grabbing 2.95.3 sources and building by running configure with
--target=powerpc-linux, but I get some missing include file errors
building libgcc2.a.  I'm on a 405GP (no fp).  Should I even bother doing
this?

2. On my intel development machine I see that libresolv.a comes from
glibc-devel-2.2.5-34.  I have gcc-2.96-110 for my compiler.  Should I go
find a version of glibc-devel that matches up with my existing 2.95.3
tools?  How will I know if its the right version?

3. Better yet, is there somewhere I can just obtain a reasonable tool
chain that's ready-built for my target machine?  Complete with libraries?

Sorry for the newbie type questions.  I have the "Using and Porting GNU
CC" book, but am finding it a little too Stallman-esque to follow.  Anyone?

Thanks!

Chris Johnson


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Tools question

[Wolfgang Denk]

Dear Chris,

in message <3FC24EB1.60106@gcctech.com> you wrote:
>
> 1. Do I really need to go back and build my own tool chain?  I've tried

Yes, you do - at least if  you  want  to  make  sure  you  completely
understand the technology and that you will in all situations be able
to build your tools from scratch.

> 2. On my intel development machine I see that libresolv.a comes from
> glibc-devel-2.2.5-34.  I have gcc-2.96-110 for my compiler.  Should I go
> find a version of glibc-devel that matches up with my existing 2.95.3
> tools?  How will I know if its the right version?

If you stick with your existing toolchain you must find a version  of
glibc-devel  that  matches your glibc. The compiler version is not so
much interesting here.

> 3. Better yet, is there somewhere I can just obtain a reasonable tool
> chain that's ready-built for my target machine?  Complete with libraries?

Did you ever have a look at our ELDK? It's free for download,  and  a
lot  of projects seem to be using it (and of course we use it ourself
for a couple of projects, too).

Please see http://www.denx.de/twiki/bin/view/DULG/ELDK for details.

> Sorry for the newbie type questions.  I have the "Using and Porting GNU
> CC" book, but am finding it a little too Stallman-esque to follow.  Anyone?

Karim Yaghmour: "Building Embedded  Linux  Systems"  [Paperback:  400
pages,  O'Reilly  &  Associates;  (May  2003);  ISBN  059600222X]  is
definitely worth reading.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"This isn't brain surgery; it's just television."   - David Letterman

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Tools question

[Dan Kegel]

Christopher R. Johnson wrote:
> This is probably way too big a question to ask here, but I'm hoping
> someone can help me.  I have inherited a gcc 2.95.3 cross development
> tool chain, which has been working fine to build for my powerpc-linux
> target machine.  I'm building the kernel and user programs fine.  I'm
> beginning to find as I add things in that I'm missing libraries.  Today
> its libresolv which I need for pump.  Some questions:
>
> 1. Do I really need to go back and build my own tool chain?  I've tried
> grabbing 2.95.3 sources and building by running configure with
> --target=powerpc-linux, but I get some missing include file errors
> building libgcc2.a.  I'm on a 405GP (no fp).  Should I even bother doing
> this?

Only if you run into trouble with your old compiler.
If and when you decide to rebuild the compiler, see
http://kegel.com/crosstool for a recipe you can follow.

> 2. On my intel development machine I see that libresolv.a comes from
> glibc-devel-2.2.5-34.  I have gcc-2.96-110 for my compiler.  Should I go
> find a version of glibc-devel that matches up with my existing 2.95.3
> tools?  How will I know if its the right version?

Again, http://kegel.com/crosstool (if you study it, and compare it
with Karim's book) will help show you how to build the glibc of your
choice.

> 3. Better yet, is there somewhere I can just obtain a reasonable tool
> chain that's ready-built for my target machine?  Complete with libraries?

That same URL can show how to build a reasonable toolchain for the ppc405
without any thought on your part, if you choose to not read and
understand the script.  It's always better to read and understand, though.

> Sorry for the newbie type questions.  I have the "Using and Porting GNU
> CC" book, but am finding it a little too Stallman-esque to follow.  Anyone?

Your question is quite reasonable.

BTW, which glibc does your toolchain use?
- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Tools question

[Wells, Charles]

Chris,

There are existing tool chains that I'm sure someone else will recommend.  I
built my own and I prefer that approach.  You learn a lot by doing it.  A
good reference for building tool chains can be found in the book "Building
Embedded Linux Systems" by Karim Yaghmour.  See
<http://www.oreilly.com/catalog/belinuxsys/>.

Regards,
Charlie

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/