[issue166] Segmentation fault on "smart update"

Jeff Johnson n3npq at mac.com
Tue Jun 27 11:02:55 PDT 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Jun 27, 2006, at 6:16 AM, Werner Flamme wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jeff Johnson schrieb am 16.06.2006 16:38:
>>
>> On Jun 16, 2006, at 10:31 AM, Werner Flamme wrote:
>>
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Jeff Johnson at Labix Tracker schrieb am 16.06.2006 15:13:
>>>>> Jeff Johnson <n3npq at mac.com> added the comment:
>>>>>
>>>>> On Jun 16, 2006, at 8:59 AM, Michael Vogt at Labix Tracker wrote:
>>>>>
>>>>>> Michael Vogt <michael.vogt at ubuntu.com> added the comment:
>>>>>>
>>>>>> So it crashs somewhere in librpmdb:
>>>>>>
>>>>>> 0x00002aaaad7252f0 in rpmfiBuildFNames () from /usr/lib64/
>>>>>> librpmdb-4.1.so
>>>>>> (gdb) backtrace
>>>>>> #0  0x00002aaaad7252f0 in rpmfiBuildFNames () from /usr/lib64/
>>>>>> librpmdb-4.1.so
>>>>>> #1  0x00002aaaad5bf198 in rpmHeaderGetEntry () from /usr/lib64/
>>>>>> librpm-4.1.so
>>>>>> #2  0x00002aaaad460c4f in tagNumFromPyObject () from
>>>>>> /usr/lib64/python2.4/site-packages/rpmmodule.so
>>>>>> #3  0x00002aaaaac51c76 in PyEval_EvalFrame () from /usr/lib64/
>>>>>> libpython2.4.so.1.0
>>>>>> [..]
>>>>>>
>>>>>> Does this help the rpm gurus get a idea what is wrong?
>>>>>>
>>>>> Almost.
>>>>>
>>>>> Do you have a ptr to the package that caused the problem?
>>>>>
>>>>> It's likelier a build than an install problem.
>>>>>
>>>>> 73 de Jeff
>>>>>
>>>> rz36:~ # ldconfig -p | grep librpmdb
>>>>         librpmdb-4.1.so (libc6,x86-64) => /usr/lib64/ 
>>>> librpmdb-4.1.so
>>>> rz36:~ # rpm -q rpm
>>>> rpm-4.1.1-222
>>>>
>>>> Still running SUSE 10.0 x86_64 ;-)
>>>>
>>
>> I'm looking for the package that triggers the problem rather than the
>> version of the rpm package.
>>
>> rpmHeaderGetEntry() is a wrapper that conceals the fact that rpm
>> saves file
>> names as a (DIRNAME, BASENAME, DIRINDEX) triple rather than a a path.
>>
>> My guess is that there is something different with the file paths in
>> that specific package.
>>
>> 73 de Jeff
>>
>
> Jeff,
>
> do I have to do this? If yes, what must I do?
>

I'd like to see the package that was being processed wen the segfault  
(and the traceback above) was generated.

> In the meantime, I installed smart 0.42:
>
> rz36:~ # smart update --log-level=debug
> debug: Failed fetching channel 'Packman 3rd Party Package Repository'
> Segmentation fault
> ###################################################################### 
> ########
>   ( 98%)
> rz36:~ # rpm -qa | grep smart
> smart-addons-0.42-1.guru.suse100
> apt-smartclean-1.0-0.oc2pus.2
> smart-0.42-1.guru.suse100
> smart-gui-0.42-1.guru.suse100
> smart-ksmarttray-0.42-1.guru.suse100
> rz36:~ # rpm -qa | grep py
> python-numeric-24.0-2
> python-ctypes-0.9.9.3-1.guru.suse100
> python-cairo-1.0.2-14
> python-qt-3.5.3-2.7
> kdebindings3-python-3.5.3-2.7
> python-2.4.1-3
> python-logilab-common-0.11.0-3
> python-curses-2.4.1-3
> python-gdbm-2.4.1-3
> python-ldap-2.2.0-1.guru.suse100
> pyweblib-1.3.3-4
> python-kde-extensions-0.4.0-1.guru.suse100
> pylint-0.7.0-3
> python-wxGTK-2.6.1.0-4
> python-tk-2.4.1-3
> python-smbpasswd-1.0.1-2.guru.suse100
> mmpython-0.4.9-1
> rpm-python-4.1.1-222
> python-elementtree-1.2.6-2
> libxml2-python-2.6.23-1.guru.suse100
> python-doc-2.4.1-3
> python-imaging-1.1.4-298
> python-gtk-2.8.2-21
> pyxml-0.8.4-4
> python-xml-2.4.1-3
> python-32bit-2.4.1-3
> libxslt-python-1.1.15-2.guru.suse100
> python-zopeinterface-3.0.1-2
> python-crypto-2.0-4
> rz36:~ #
>
> May one of these packages be the cause?
>

It's likely to be a package in the channel 'Packman 3rd Party Package  
Repository'.

73 de Jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEoXLVuHNkGyA5spERAr+pAJsH2YriljNnbtankNG9A2Rg7iGqgwCcDG09
uoxAuaVki8yNN9iWspt8x8A=
=wSsq
-----END PGP SIGNATURE-----



More information about the Smart mailing list