mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: jes@trained-monkey.org, Adrian Bunk <bunk@stusta.de>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: xconfig segfault
Date: Mon, 20 Nov 2006 15:43:59 -0800	[thread overview]
Message-ID: <20061120154359.9013bace.randy.dunlap@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611210029140.6242@scrub.home>

On Tue, 21 Nov 2006 00:30:36 +0100 (CET) Roman Zippel wrote:

> Hi,
> 
> On Mon, 20 Nov 2006, Randy Dunlap wrote:
> 
> > > I cannot reproduce this. Could you try to run qconf within gdb for a
> > > backtrace (adding -g to HOST_EXTRACFLAGS might get more useful output).
> > 
> > Sure, let me know what you want next.
> 
> Hmm, an uninitialize field is IMO the only thing that could go wrong here.

Great, that fixes it.  Thanks!

> bye, Roman
> 
> ---
>  scripts/kconfig/qconf.cc |    1 +
>  1 file changed, 1 insertion(+)
> 
> Index: linux-2.6/scripts/kconfig/qconf.cc
> ===================================================================
> --- linux-2.6.orig/scripts/kconfig/qconf.cc
> +++ linux-2.6/scripts/kconfig/qconf.cc
> @@ -1259,6 +1259,7 @@ void ConfigSearchWindow::search(void)
>   * Construct the complete config widget
>   */
>  ConfigMainWindow::ConfigMainWindow(void)
> +	: searchWindow(0)
>  {
>  	QMenuBar* menu;
>  	bool ok;
> -


---
~Randy

      reply	other threads:[~2006-11-20 23:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20  0:12 Randy Dunlap
2006-11-20  0:41 ` Adrian Bunk
2006-11-20  0:47   ` Randy Dunlap
2006-11-20 18:24     ` Randy Dunlap
2006-11-20 21:57       ` Roman Zippel
2006-11-20 23:19         ` Randy Dunlap
2006-11-20 23:30           ` Roman Zippel
2006-11-20 23:43             ` Randy Dunlap [this message]

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=20061120154359.9013bace.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=bunk@stusta.de \
    --cc=jes@trained-monkey.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome