|
Bugzilla – Full Text Bug Listing |
| Summary: | zypper segfaults | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Dominique Leuenberger <dimstar> |
| Component: | libzypp | Assignee: | Jan Kupec <jkupec> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P2 - High | CC: | burnus, vuntz |
| Version: | Factory | ||
| Target Milestone: | RC 1 | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Community User | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | The output of bt full | ||
Created attachment 254847 [details]
The output of bt full
I guess i know where is the problem. Thanx :O) Ján, I'm amazed that you can read anything out of the mess of that backtrace... I've seen more readable ones than this one. *** Bug 448280 has been marked as a duplicate of this bug. *** Fixed in svn, to be in zypper 1.0.1. (In reply to comment #3 from Dominique Leuenberger) > I'm amazed that you can read anything out of the mess of that backtrace... I've > seen more readable ones than this one. Well, the "#1 ... in printPkgInfo at ... src/info.cc:169" and "theone = {_pimpl = {_dptr = {px = 0x0, pn = {pi_ = 0x0}}}}" immediately refreshed my memory, that there was something i planned to fix, but i did not manage to come back to it :O) *** Bug 448402 has been marked as a duplicate of this bug. *** submitted |
yeah ;) I got zypper to segfault (after a long time again.. and reproducible) gdb zypper | tee log (gdb) run info compiz-plugins-dmx Starting program: /usr/bin/zypper info compiz-plugins-dmx [Thread debugging using libthread_db enabled] Loading repository data... Reading installed packages... Information for package compiz-plugins-dmx: Program received signal SIGSEGV, Segmentation fault. zypp::PoolItem::resolvable (this=0x7fffffffa040) at /usr/include/boost/intrusive_ptr.hpp:94 in /usr/include/boost/intrusive_ptr.hpp (gdb) bt full The full backtrace is attached to this bugreport.... (it seems actually to be one of the fewer packages that's segfaulting.. so it might be in it's description.. nevertheless: zypper is not allowed to segfault on unexpected input).