From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub-setup Segmentation fault
Date: Mon, 6 Aug 2007 18:44:12 +0200 [thread overview]
Message-ID: <20070806164412.GA9171@aragorn> (raw)
In-Reply-To: <A3F18E63267C4D9C8068958F10B9E701@MediaDator>
On Sun, Aug 05, 2007 at 02:14:28PM +0200, Magnus Granberg wrote:
> >>>Could you try the attached patch?
> >>>
> >>>--
> >>>Robert Millan
> >>>
> >>It did't fix the Segmentation fault :(
> >
> >It wasn't supposed to. Did you see what the patch is doing?
> >
> >--
> >Robert Millan
>
> grub-setup: info: prefix = /grub
> grub-setup: info: changing current directory to /dev/mapper
> grub-setup: info: 2 root_dev = vg-boot
> grub-setup: info: getting the size of /boot/grub/boot.img
> grub-setup: info: reading /boot/grub/boot.img
> grub-setup: info: getting the size of /boot/grub/boot.img
> grub-setup: info: getting the size of /boot/grub/core.img
> grub-setup: info: reading /boot/grub/core.img
> grub-setup: info: getting the size of /boot/grub/core.img
> Segmentation fault
Sounds like I made the wrong guess, then. You need to figure out where's
that null pointer coming from. Doesn't seem to be root_dev..
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2007-08-06 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 12:14 grub-setup Segmentation fault Magnus Granberg
2007-08-06 16:44 ` Robert Millan [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-08 3:08 Magnus Granberg
2007-08-12 14:39 ` Robert Millan
2007-08-04 18:13 Magnus Granberg
2007-08-05 10:00 ` Robert Millan
2007-08-04 2:37 Magnus Granberg
2007-08-04 9:56 ` Robert Millan
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=20070806164412.GA9171@aragorn \
--to=rmh@aybabtu.com \
--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.