All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Isaac M. Marcos" <isaacmarcos100010@gmail.com>
To: grub-devel@gnu.org
Cc: Pavel Roskin <proski@gnu.org>
Subject: Re: grub-probe gets a segfault
Date: Mon, 12 May 2008 09:46:42 -0430	[thread overview]
Message-ID: <200805120946.44036.isaacmarcos100010@gmail.com> (raw)
In-Reply-To: <1210284927.9311.9.camel@dv>

On Thursday 08 May 2008 17:45:27 Pavel Roskin wrote:
> On Thu, 2008-05-08 at 11:53 -0430, Isaac M. Marcos wrote:
> > >  Try the CVS version.  Try debugging the codedump.
> >

Done, same segfault.

> As for debugging, I see you have found something already.
>
> > Good, next step?
>
> Try the version from CVS.  Describe the problem in a concise way, so
> that nobody has to go through the whole discussion in the Debian bug
> tracker.  Try using grub-probe on paths that are not on LVM (like a
> mounted floppy or a flash drive).

Neither" /" or "/boot" are in a LVM partition!!!!!!!!!

cvs version 
# ./grub-probe -t device /
	Violación de segmento
# ./grub-probe -t device /boot
	Violación de segmento
# ./grub-probe -t device /dev/cdrom		# cd
	Violación de segmento
# ./grub-probe -t device /fd0				# floppy
	Violación de segmento
# ./grub-probe -t device dvd				# dvd
	Violación de segmento
# ./grub-probe -t device /dev/	sdg1			# USB pen drive
	Violación de segmento
# ./grub-probe help						# ?? anything
	Violación de segmento
# ./grub-probe -help
	Works
# ./grub-probe --help
	Works

system version
# grub-probe -t device /
	Violación de segmento
# grub-probe -t device /boot
	Violación de segmento
# grub-probe help						# ?? again
	Violación de segmento
# grub-probe -help
	Works ok!

Same commands tested on two other machines (one with lvm's one without)
All commands don't segfault on the system version (not cvs).

Could you make anything out of this?
Does this help in any way?

-- 
Isaac M. Marcos
GPG key 0xC9045C1B
5633 ECAF 44B1 8A5D 9371 DCDA 4620 A016 C904 5C1B

The only place success comes before work is in the dictionary.
VINCE LOMBARDI



  parent reply	other threads:[~2008-05-12 14:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08  9:24 grub-probe gets a segfault Isaac M. Marcos
2008-05-08 15:55 ` Pavel Roskin
2008-05-08 16:23   ` Isaac M. Marcos
2008-05-08 22:15     ` Pavel Roskin
2008-05-09 13:02       ` Robert Millan
2008-05-09 16:43         ` Isaac M. Marcos
2008-05-09 20:56           ` Pavel Roskin
2008-05-12 13:44             ` Isaac M. Marcos
2008-05-15 22:45               ` Pavel Roskin
2008-05-16 17:48                 ` Isaac Marcos
2008-05-16 18:02                   ` Pavel Roskin
2008-05-22  0:50                     ` Isaac M. Marcos
2008-05-22  1:06                       ` Pavel Roskin
2008-05-22 10:52                       ` Pavel Roskin
2008-05-24  0:10                         ` Isaac M. Marcos
2008-05-27 20:26                           ` Pavel Roskin
2008-05-28 13:36                         ` Robert Millan
2008-05-28 18:28                           ` Isaac M. Marcos
2008-05-30  3:59                             ` Pavel Roskin
2008-05-12 14:16       ` Isaac M. Marcos [this message]
2008-05-20 16:37         ` Jeff Chua
2008-05-20 19:53           ` Pavel Roskin
2008-05-21  2:22             ` Jeff Chua

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=200805120946.44036.isaacmarcos100010@gmail.com \
    --to=isaacmarcos100010@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=proski@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.