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:19:31 -0800 [thread overview]
Message-ID: <45623803.7070103@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611202254200.6242@scrub.home>
Roman Zippel wrote:
> Hi,
>
> On Mon, 20 Nov 2006, Randy Dunlap wrote:
>
>> I found the problem patch, but not the root cause.
>>
>> The xconfig segfault begins in 2.6.19-rc5-git3 (-git2 is OK).
>> A relatively simple Kconfig change causes it (but why?).
>>
>> (Note: The running kernel doesn't matter, just which kernel tree
>> is being viewed/config-ed.)
>>
>> If I back out the patches below, -git3 (xconfig ^F find/search)
>> works for me.
>
> 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.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46953334203536 (LWP 23635)]
0x00000000004289bc in ConfigMainWindow::searchConfig ()
(gdb) bt
#0 0x00000000004289bc in ConfigMainWindow::searchConfig ()
#1 0x0000000000428ae2 in ConfigMainWindow::qt_invoke ()
#2 0x00002ab42ab8b79c in QObject::activate_signal ()
from /usr/lib64/libqt-mt.so.3
#3 0x00002ab42ab8c4b3 in QObject::activate_signal ()
from /usr/lib64/libqt-mt.so.3
#4 0x00002ab42ae889b3 in QAction::qt_invoke () from /usr/lib64/libqt-mt.so.3
#5 0x00002ab42ab8b79c in QObject::activate_signal ()
from /usr/lib64/libqt-mt.so.3
#6 0x00002ab42ae6d628 in QSignal::signal () from /usr/lib64/libqt-mt.so.3
#7 0x00002ab42aba42a5 in QSignal::activate () from /usr/lib64/libqt-mt.so.3
#8 0x00002ab42ab31a45 in QAccelPrivate::activate ()
from /usr/lib64/libqt-mt.so.3
#9 0x00002ab42ab333e2 in QAccelManager::dispatchAccelEvent ()
from /usr/lib64/libqt-mt.so.3
#10 0x00002ab42ab338fc in qt_dispatchAccelEvent () from /usr/lib64/libqt-mt.so.3
#11 0x00002ab42ab35d7a in QApplication::notify () from /usr/lib64/libqt-mt.so.3
#12 0x00002ab42ab31fce in QAccelManager::tryAccelEvent ()
from /usr/lib64/libqt-mt.so.3
#13 0x00002ab42ab323ac in qt_tryAccelEvent () from /usr/lib64/libqt-mt.so.3
#14 0x00002ab42aadb39c in QETWidget::translateKeyEvent ()
from /usr/lib64/libqt-mt.so.3
#15 0x00002ab42aadc180 in QApplication::x11ProcessEvent ()
from /usr/lib64/libqt-mt.so.3
#16 0x00002ab42aaeb22f in QEventLoop::processEvents ()
from /usr/lib64/libqt-mt.so.3
#17 0x00002ab42ab49691 in QEventLoop::enterLoop () from /usr/lib64/libqt-mt.so.3
#18 0x00002ab42ab4953a in QEventLoop::exec () from /usr/lib64/libqt-mt.so.3
#19 0x0000000000425e23 in main ()
(gdb)
--
~Randy
next prev parent reply other threads:[~2006-11-20 23:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 0:12 xconfig segfault 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 [this message]
2006-11-20 23:30 ` Roman Zippel
2006-11-20 23:43 ` 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=45623803.7070103@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