On Thursday 18 May 2006 14:27, Lubomir Kundrak wrote:
> On Sat, May 13, 2006 at 06:38:26AM +0200, Yoshinori K. Okuji wrote:
> > Message-Id: <[EMAIL PROTECTED]>
> >
> > Great!
> >
> > I guess it is necessary to compile the binary with -O0 or -O1 to get a
> > reasonable backtrace... I'd appreciate if
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
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.
>
>
On Sat, May 13, 2006 at 06:38:26AM +0200, Yoshinori K. Okuji wrote:
> Message-Id: <[EMAIL PROTECTED]>
>
> Great!
>
> I guess it is necessary to compile the binary with -O0 or -O1 to get a
> reasonable backtrace... I'd appreciate if you can write a HOWTO. :)
On i386 GCC generates full stack fram
Thanks, I now have gdb running as I expect in my module.
David
Lubomir Kundrak wrote:
I noticed, that when any segment is 0 bytes long and starts
at 0x0, gdb desn't resolve symbols correctly.
I have motified the gmodule.pl to reflect this.
Please check an updated version.
regards,
lubo
___
ROTECTED]>
> X-Virus-Scanned: Symantec AntiVirus Scan Engine
> Subject: Re: Debugging GRUB2 with GDB and QEMU
> X-BeenThere: grub-devel@gnu.org
> X-Mailman-Version: 2.1.5
> Precedence: list
> Reply-To: The development of GRUB 2
> List-Id: The development of GRUB 2
> Li
ge d'origine-
> De : [EMAIL PROTECTED] [mailto:grub-devel-
> [EMAIL PROTECTED] De la part de Lubomir Kundrak
> Envoyé : vendredi 12 mai 2006 15:20
> À : grub-devel@gnu.org
> Objet : Debugging GRUB2 with GDB and QEMU
>
> I wrote some GDB macros that might be helpful
Hi, thanks for the help with debugging modules. I have a module that I
created and still need a little assistance in getting gdb to break in my
module's grub_cmd_*. I am able to connect to QEMU with gdb and when I
load the module, gdb loads the symbol table for my module.
But, when I set a
Hi Lubomir,
Thanks for the scripts. It is just what I was looking for.
Meanwhile, since my last email, I have done something foolish.
I've coded in grub's sources just the same algorithm you provide but
I've clumbered the sources with new functions those purpose is only for
debugging while you ar
On Friday 12 May 2006 15:20, Lubomir Kundrak wrote:
> I wrote some GDB macros that might be helpful for people
> that want to debug GRUB 2 modules with QEMU. [1]
Great!
I guess it is necessary to compile the binary with -O0 or -O1 to get a
reasonable backtrace... I'd appreciate if you can write
I wrote some GDB macros that might be helpful for people
that want to debug GRUB 2 modules with QEMU. [1]
[1] http://NetBSD.sk/~lkundrak/misc/grub2-gdb/
The file genmk.rb.diff is a patch to makefile-generator
script, that makes the build system leave output files with
debugging information. Of co
11 matches
Mail list logo