All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Re: Bug in read_handler_list (autoloading) ???
Date: Sat, 14 Nov 2009 22:11:31 +0100	[thread overview]
Message-ID: <1258233091.2749.2.camel@fz.local> (raw)
In-Reply-To: <20091114153519.GA7084@thorin>

Am Samstag, den 14.11.2009, 16:35 +0100 schrieb Robert Millan:
> On Fri, Nov 13, 2009 at 11:43:52PM +0100, Vladimir 'phcoder' Serbinenko wrote:
> > Felix Zielcke wrote:
> > > Am Donnerstag, den 12.11.2009, 21:46 +0530 schrieb BVK:
> > >   
> > >> Valgrind log is attached. It also reported invalid free for the same place.
> > >>
> > >> BTW, valgrind is run as
> > >>
> > >>     sudo valgrind -v --log-file=/tmp/valgrind.log ./grub-emu
> > >>     
> > >
> > > Here's a grub-emu tested patch to fix this
> > >
> > >
> > >   
> > Why are all handlers are removed on normal.mod unload? If user e.g.
> > relies on special terminal he may lose terminal completely. I would say
> > it's better not to touch already loaded modules. I temporarily unmerged
> > it from experimental. We can remerge it once issues are fixed
> 
> Did you unmerge Felix' fix, or the original prefix move fix?

I didn't commit my fix.
He reverted your original merge of this.

> My goal was to make command and file-system auto-completion not break when
> $prefix is changed.  Handlers are not the important change in my initial
> patch, and if it's problematic it can be discarded IMO.
> 


-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer




  reply	other threads:[~2009-11-14 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11  4:00 Bug in read_handler_list (autoloading) ??? BVK
2009-11-12 16:16 ` BVK
2009-11-12 20:36   ` [PATCH] " Felix Zielcke
2009-11-12 20:51     ` Robert Millan
2009-11-13 22:43     ` Vladimir 'phcoder' Serbinenko
2009-11-14 15:35       ` Robert Millan
2009-11-14 21:11         ` Felix Zielcke [this message]
2009-11-15 11:10           ` Robert Millan
2010-01-07 18:48             ` 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=1258233091.2749.2.camel@fz.local \
    --to=fzielcke@z-51.de \
    --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.