From: Lubomir Kundrak <lkundrak@skosi.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Debugging GRUB2 with GDB and QEMU
Date: Fri, 19 May 2006 12:16:58 +0200 [thread overview]
Message-ID: <20060519101658.GC60590@meta.morph.sk> (raw)
In-Reply-To: <1147959325.23666.3.camel@diesel>
On Thu, May 18, 2006 at 08:35:25AM -0500, Hollis Blanchard wrote:
>
> On Thu, 2006-05-18 at 14:27 +0200, Lubomir Kundrak wrote:
> > On Sat, May 13, 2006 at 06:38:26AM +0200, Yoshinori K. Okuji wrote:
> >
> > On i386 GCC generates full stack frames even with -O optizations.
> > It only omits frame pointer on architectures on which it doesn't
> > interfere with debugging.
> >
> > I started a small HOWTO recently, so here is it: [1]. Enjoy :o)
> > [1] http://NetBSD.sk/~lkundrak/misc/grub2-gdb/howto.html
>
> This looks like very interesting stuff, but wouldn't it be better to put
> this in the wiki? Please see http://grub.enbug.org.
>
> -Hollis
Yeah, I thought about it, but I don't have Internet connection at home,
so I am unable to edit it in wiki when offline, so it's easier for me
to have it as a standalone file. If anyone wants to change anything,
I will accept a patch for that hapilly.
--
o Lubomir Kundrak
*O* <lkundrak@skosi.org>, http://skosi.org/~lkundrak/
(_) SKOSI -- Slovak OpenSource Initiative
next prev parent reply other threads:[~2006-05-19 10:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 13:20 Debugging GRUB2 with GDB and QEMU Lubomir Kundrak
2006-05-13 4:38 ` Yoshinori K. Okuji
2006-05-18 12:27 ` Lubomir Kundrak
2006-05-18 13:35 ` Hollis Blanchard
2006-05-19 10:16 ` Lubomir Kundrak [this message]
2006-05-19 11:25 ` Yoshinori K. Okuji
2006-05-13 5:28 ` RE : " Eric Salomé
2006-05-13 18:45 ` devShadow
2006-05-14 14:01 ` Lubomir Kundrak
2006-05-17 21:15 ` David Johnson
2006-05-13 22:16 ` RE : " Eric Salomé
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=20060519101658.GC60590@meta.morph.sk \
--to=lkundrak@skosi.org \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.