From: John Van Horne <JohnVan.Horne@cosinecom.com>
To: "'gdb@sourceware.cygnus.com'" <gdb@sourceware.cygnus.com>
Subject: what to do when upgrading Linux kernel
Date: Wed, 14 Feb 2001 11:07:00 -0000 [thread overview]
Message-ID: <7EB7C6B62C4FD41196A80090279A29113D740A@exchsrv1.cosinecom.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1771 bytes --]
Title: what to do when upgrading Linux kernel
I'm hoping someone can help me with the following problem.
I've got Yellow Dog Linux, 2.2.18, and gdb 4.18. I install Linux kernel 2.4-test1, and
gdb no longer works. When I try to debug a program, even a very simple "hello
world" program, it says something like "Can't insert breakpoint -1. Can't access
memory at 0x6c6c2c07". If I link the test program statically, and try to run gdb on
it, I get "Program received SIGTRAP Trace/Breakpoint signal. 0x6c6c2f7d in ??()".
I figure that I've got a library incompatibility problem. Do I need to recompile
and reinstall glibc for the new kernel, and then recompile gdb? Will that be enough,
or are there other steps one should take when upgrading a Linux kernel?
I know that 2.4 test1 is not the latest 2.4 kernel available for the PPC. For reasons
beyond my control, I'm stuck with it, at least for the near future. Is it possible that
gdb simply won't run on this kernel?
Thanks,
-John
------------------------------------------------------------------------------------------------------------------------
John Van Horne                      voice: 650-628-4148
Software Tools Engineer               fax:     650-637-2411
CoSine Communications, Inc.                  cell:    650-346-0401
< http://www.cosinecom.com > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â email:Â jvhorne@cosinecom.com
------------------------------------------------------------------------------------------------------------------------
next reply other threads:[~2001-02-14 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 11:07 John Van Horne [this message]
2001-02-14 11:55 ` Kevin Buettner
2001-02-16 10:51 John Van Horne
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=7EB7C6B62C4FD41196A80090279A29113D740A@exchsrv1.cosinecom.com \
--to=johnvan.horne@cosinecom.com \
--cc=gdb@sourceware.cygnus.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