From: Pete/Piet Delaney <pete@bluelane.com>
To: "Discussion list for crash utility usage,
maintenance and development" <crash-utility@redhat.com>
Cc: Dave Anderson <anderson@redhat.com>
Subject: Re: [Kgdb-bugreport] Problem getting kgdb to read kernel symbols. addresses shifted?
Date: Fri, 28 Sep 2007 17:32:46 -0700 [thread overview]
Message-ID: <46FD9D2E.3020504@bluelane.com> (raw)
In-Reply-To: <sjmodfmgx5q.fsf@pgpdev.ihtfp.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Derek Atkins wrote:
Dave, I thought you would likely know what's going on here.
How about helping out Derek? Sounds like a RedHat'ism and
I kinda recall your mentioning it and apologizing for it
as an unfortunate RedHat directive.
- -piet
> ebiederm@xmission.com (Eric W. Biederman) writes:
>
>> Derek Atkins <warlord@MIT.EDU> writes:
>>
>>> Well, gdb agrees with System.map, so I'm sure that gdb itself is
>>> okay. It's certainly possible that that the kgdb stub is weird,
>>> but /proc/kallsyms doesn't match System.map, and THAT'S what's
>>> confusing me most of all.
>> Ok. So we must have a relocatable kernel that figures it has been
>> relocated. Interesting.
>>
>> What is your bootloader?
>
> GRUB
>
>> What is your kernel version?
>
> 2.6.22.5-76_kgdb0.fc7-i686
>
>> What is your kernel config?
>
> See the attached .config file.
>
>> The only time I would expect to see what you are seeing is if
>> you are debugging the kdump kernel, which doesn't sound like
>> the case.
>
> Nope. I started with the Fedora 'i686' config and then patched
> in the kgdb patches and configuration.
>
>> If we actually have a truly offset kernel then while things
>> may not be perfect this is at least expected. I don't think
>> I have heard of anyone handling this case very well.
>
> :( Like I said before, it SEEMS to work okay by telling GDB
> to load in at a different address.
>
>>> Which was how long ago? ;)
>> Long enough ago that I don't remember when ;)
>
> Heh.
>
>> Eric
>
> -derek
>
>
>
> ------------------------------------------------------------------------
>
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Kgdb-bugreport mailing list
> Kgdb-bugreport@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG/Z0uJICwm/rv3hoRAl1uAJ9QoR5DhfUGCccgz9KFpEpHkbvaaACdGG2z
9LxB5RdtsUi9IrTKzbPpB1U=
=gQee
-----END PGP SIGNATURE-----
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2007-09-29 0:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sjmabr8j6d7.fsf@pgpdev.ihtfp.org>
[not found] ` <46FD03CD.9060404@windriver.com>
[not found] ` <sjmve9uj3d2.fsf@pgpdev.ihtfp.org>
[not found] ` <46FD1B6A.3000500@windriver.com>
[not found] ` <20070928114522.n0cdrcebykkgg408@webmail.mit.edu>
[not found] ` <46FD2CFB.9010404@windriver.com>
2007-09-28 21:45 ` [Kgdb-bugreport] Problem getting kgdb to read kernel symbols. addresses shifted? Pete/Piet Delaney
2007-09-28 22:18 ` Eric W. Biederman
2007-09-28 23:29 ` Derek Atkins
2007-09-28 23:40 ` Eric W. Biederman
2007-09-28 23:58 ` Derek Atkins
2007-09-29 0:32 ` Pete/Piet Delaney [this message]
2007-09-30 5:38 ` Vivek Goyal
2007-10-01 13:35 ` Dave Anderson
2007-10-01 18:44 ` Derek Atkins
2007-10-01 19:03 ` Dave Anderson
2007-10-01 20:35 ` Derek Atkins
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=46FD9D2E.3020504@bluelane.com \
--to=pete@bluelane.com \
--cc=anderson@redhat.com \
--cc=crash-utility@redhat.com \
--cc=pdelaney@bluelane.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