>>boot_file=, core_file=0x805cb2a "core.img",
>> root=0x8067050 "vg-boot", dest=0x0, must_embed=1)
>>at util/i386/pc/grub-setup.c:223
>> #2 0x0804a0bc in main (argc=Cannot access memory at address 0xb
>> ) at util/i386/pc/grub-setup.c:733
>> (gdb)
>
>Could you try the attached patch?
>
>-
On 8/4/07, Robert Millan <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 03, 2007 at 11:33:38PM +0800, Bean wrote:
> > Hi,
> >
> > I have written a new command dump, it can hex dump content of file or
> > memory.
> >
> > usage:
> >
> > dump [-s skip] [-n length] { FILE | (mem) }
> >
> > The output look j
On Sat, Aug 04, 2007 at 04:37:03AM +0200, Magnus Granberg wrote:
> Starting program:
> /sbin/grub-setup --directory=/boot/grub --device-map=/boot/grub/device.map
> /dev/md0
>
> Program received signal SIGSEGV, Segmentation fault.
> grub_device_open (name=0x0) at kern/device.c:38
> 38
On Fri, Aug 03, 2007 at 11:33:38PM +0800, Bean wrote:
> Hi,
>
> I have written a new command dump, it can hex dump content of file or memory.
>
> usage:
>
> dump [-s skip] [-n length] { FILE | (mem) }
>
> The output look just like command hexdump.
I see that the output of hexdump is the same a
