From: "Isaac M. Marcos" <isaacmarcos100010@gmail.com>
To: grub-devel@gnu.org
Subject: Re: grub-probe gets a segfault
Date: Thu, 8 May 2008 11:53:23 -0430 [thread overview]
Message-ID: <200805081153.24513.isaacmarcos100010@gmail.com> (raw)
In-Reply-To: <1210262124.23398.18.camel@dv>
On Thursday 08 May 2008 11:25:24 Pavel Roskin wrote:
> On Thu, 2008-05-08 at 04:54 -0430, Isaac M. Marcos wrote:
> > I have open a ticket in bugs.debian.org numbered 478401 referring to a
> > segfault that grub-probe is getting.
>
> URL for convenience of others:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478401
>
> > Robert Millan suggested to bring this problem here.
> >
> > What should i do?
>
> Try running update-grub manually. Try reproducing the crash in a way
> that doesn't involve anything Debian specific.
Does:
# grub-probe -t device /
involve anything Debian specific ????????
> Try the CVS version. Try debugging the codedump.
Sure, only if i knew how, :-)
> > Am i in the right place?
>
> Yes
Good, next step?
--
Isaac M. Marcos
next prev parent reply other threads:[~2008-05-08 16:23 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 [this message]
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
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=200805081153.24513.isaacmarcos100010@gmail.com \
--to=isaacmarcos100010@gmail.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.