linux-kernel - Re: qconf: reproducible segfault

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <5a4c581d0701051328i49fb13ffse15c41b6531dfd71@mail.gmail.com>
Date:	Fri, 5 Jan 2007 22:28:52 +0100
From:	"Alessandro Suardi" <alessandro.suardi@...il.com>
To:	gorcunov@...il.com
Cc:	"kernel list" <linux-kernel@...r.kernel.org>
Subject: Re: qconf: reproducible segfault

On 1/5/07, Cyrill V. Gorcunov <gorcunov@...il.com> wrote:
> On Friday 05 January 2007 00:16, you wrote:
> |  On 1/4/07, Cyrill V. Gorcunov <gorcunov@...il.com> wrote:
> |  > Hi,
> |  > there is SIGSEGV happens in qconf.cc:995
> |  >
> |  >         str += print_filter(sym->name);
> |  >
> |  > but sym points to 0x1. To reproduce the error just do:
> |  >
> |  > 1) make xconfig (with Options->Show Debug Info unchecked)
> |  > 2) go to Networking->Networking Options->Network packet filtering framework (Netfilter)->
> |  >    Network packet filtering framework (Netfilter) and the line "<| .." must be selected
> |  >    then just turn on Options->Show Debug info menu and you'll get:
> |  >
> |  >         make[1]: *** [xconfig] Segmentation fault
> |  >         make: *** [xconfig] Error 2
> |
> |  Cyrill, Randy - I feel like an idiot but I can't really reproduce this :(
> |
> |  I'm trimming lkml from the CC list to upload and attach two screenshots
> |   where I enabled Show Debug Info at what I guess are the two possible
> |   interpretations of where the Select highlight should be - and neither
> |   cause a core dump for me.
> |
> |  What am I mistaking ?
> |
> |  Thanks, ciao,

> Hi Alessandro,
>
> see enveloped scrshot to keep in mind how the qconf is looking at moment we
> get SYGSEGV error - you just need to set Options->Show Debug and oops ;)
> I don't know may be QT dev version does handling such exceptions itself and if
> SYGSEVG happens it just ignore it... But the qconf really have the error :(.

That's ok, apparently FC6's qt-devel-3.3.7 libs are capable of
 handling the problem (I can bring qconf to the exact screen
 you showed, Options->Show Debug Info does _not_ crash).

And of course it's better to fix the problem in qconf.cc rather
 than letting qt libs handle it :)

Thanks,

--alessandro

 "but I thought that I should let you know
  the things that I don't always show
  might not be worth the time it took"

     (Steve Wynn, 'If My Life Was An Open Book')
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/