https://bugzilla.novell.com/show_bug.cgi?id=439685
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=439685#c5
Stefan Hundhammer changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|yast2-maintainers@suse.de |jkupec@novell.com
Status|NEEDINFO |NEW
Component|YaST2 |libzypp
Info Provider|mirkop82@gmail.com |
--- Comment #5 from Stefan Hundhammer 2008-10-29 08:35:41 MDT ---
Jano, this looks very much like a crash in the ZYPP query engine to me:
Frame 3: (dataiterator_step+0xb30) [0xb6f2bee0]
Frame 4: zypp::sat::LookupAttr::iterator::increment()
Frame 5: zypp::detail::PoolQueryIterator::matchSolvable()
Frame 6: zypp::detail::PoolQueryIterator::increment()
Frame 7: YQPkgSearchFilterView::filter()
Frame 8: YQPkgSearchFilterView::qt_metacall(QMetaObject::Call, int, void**)
Frame 9: QMetaObject::activate(QObject*, int, int, void**)
Frame 10: QMetaObject::activate(QObject*, QMetaObject const*, int, int, void**)
Frame 11: QAbstractButton::clicked(bool)
The log also says
2008-10-29 14:41:22 <1> WhiteSuSE(24300) [PoolQuery++]
PoolQuery.cc(compile):278 compiled: 1
and it's a signal 11 (SIGSEGV), not a signal 6 (abort, in C++ typically sent by
an unhandled exception), so it seems to be a real segfault, not a duplicate of
bug #403367 (crash when searching for invalid regex - unhandled exception).
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.