From: Gerald Champagne <gerald.champagne@esstech.com>
To: Jeff Harrell <jharrell@telogy.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: VisionClick debugger with Linux kernel
Date: Fri, 12 Oct 2001 11:26:53 -0500 [thread overview]
Message-ID: <3BC719CD.8060303@esstech.com> (raw)
In-Reply-To: 3BC6F26B.E386F412@telogy.com
Thanks for the response. I just found the problem last night. Their
convert utility was screwing up on files that had module_init and
module_exit routines in them, even though it wasn't compiled as a module.
I fixed it by replacing the __init and __exit macros with nothing so
the code is placed in a normal .text segment.
Gerald
Jeff Harrell wrote:
> Gerald Champagne wrote:
>
> Has anyone used the Wind River VisionClick debugger with the Linux
> kernel?
> I'm using this debugger and works great except it thinks that the
> symbols
> for some files start at address zero instead of the proper offset.
> Has anyone
> else seen this and were you able to get it to work? I'm using the
> latest tools
> from:
>
> ftp://oss.sgi.com/pub/linux/mips/redhat/7.1/RPMS/i386/toolchain-mips-20010830-1.i386.rpm
>
>
> I can't find any differences between the files that work and the
> files that
> don't work and the symbols look correct in the System.map file.
>
> Yeah, I'm working with Wind River, but I haven't gotten a solution yet.
> You know how that 8-5 centralized corporate support is though. :)
>
> Thanks!
>
> Gerald
>
> We are using a VisionIce debugger from the linux-mips kernel, although I
> am using the
> MontaVista Hardhat 2.0 tools. I am able to load the symbols after they
> have been
> generated from the Convert utility. It seems to work fine except for
> modules...haven't
> had much luck with that. Had to get a patch to view TLB mapped memory
> properly
> though.
>
> Jeff
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> \ Jeff Harrell (jharrell@telogy.com) \
> \ Telogy Networks \
> \ Broadband Access Group \
> \ \
> \ Work: (301) 515-6537 \
> \ Fax: (301) 515-6637 \
> \~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
prev parent reply other threads:[~2001-10-12 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 21:05 VisionClick debugger with Linux kernel Gerald Champagne
2001-10-12 13:38 ` Jeff Harrell
2001-10-12 16:26 ` Gerald Champagne [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=3BC719CD.8060303@esstech.com \
--to=gerald.champagne@esstech.com \
--cc=jharrell@telogy.com \
--cc=linux-mips@oss.sgi.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