mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alessandro Suardi" <alessandro.suardi@gmail.com>
To: gorcunov@gmail.com
Cc: "kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: qconf: reproducible segfault
Date: Fri, 5 Jan 2007 22:28:52 +0100	[thread overview]
Message-ID: <5a4c581d0701051328i49fb13ffse15c41b6531dfd71@mail.gmail.com> (raw)
In-Reply-To: <200701051022.59914.gorcunov@gmail.com>

On 1/5/07, Cyrill V. Gorcunov <gorcunov@gmail.com> wrote:
> On Friday 05 January 2007 00:16, you wrote:
> |  On 1/4/07, Cyrill V. Gorcunov <gorcunov@gmail.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')

  parent reply	other threads:[~2007-01-05 21:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-03 21:00 Bauke Jan Douma
2007-01-03 21:35 ` Randy Dunlap
2007-01-04  0:32 ` Alessandro Suardi
2007-01-04  9:42 ` Cyrill V. Gorcunov
     [not found]   ` <5a4c581d0701041316w83d1564rac875a1d4e0ef87a@mail.gmail.com>
     [not found]     ` <200701051022.59914.gorcunov@gmail.com>
2007-01-05 21:28       ` Alessandro Suardi [this message]
2007-01-04 17:14 ` Cyrill V. Gorcunov
2007-01-04 17:15   ` Randy Dunlap

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=5a4c581d0701051328i49fb13ffse15c41b6531dfd71@mail.gmail.com \
    --to=alessandro.suardi@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=linux-kernel@vger.kernel.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