Summary: | =dev-python/utidylib-0.2-r1 - src_test(): Segmentation fault in trial | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jonathan Lovelace <kingjon3377> |
Component: | [OLD] Unspecified | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | mgorny |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build log
gdb log showing context and backtrace Ebuild switching to a fork including patches to make tests pass updated patch to apply to more recent source |
Description
Jonathan Lovelace
2011-11-21 02:21:39 UTC
Created attachment 293255 [details]
Build log
I can't replicate this.
gentoo64 utidylib # el
Available Python interpreters:
[1] python2.5
[2] python2.6
[3] python2.7 *
gentoo64 utidylib # ebuild utidylib-0.2-r1.ebuild clean test
warning: build_py: byte-compiling is disabled, skipping.
>>> Source compiled.
* Testing of dev-python/utidylib-0.2-r1 with CPython 2.7...
PYTHONPATH=build-2.7/lib trial tidy
tidy.test_tidy
TidyTestCase
test_badOptions ... [OK]
test_encodings ... [OK]
test_errors ... [OK]
test_options ... [OK]
test_parse ... [OK]
a seg fault could be something quite erroneous in your system. Try unmerging, re-emerging, ensure your system has been fsck'd. The easiest way to avoid that is to make your $PORTAGE_TMPDIR on a different partition. I doubt this is a bug
utidylib isn't previously installed on my system, so I can't unmerge it. But I've unmerged and re-emerged htmltidy (according to dmesg, the segfault comes somewhere in libtidy-0.99.so.0.0.0, installed by htmltidy). I've marked my root FS to fsck on my next reboot, but I also confirmed this with PORTAGE_TMPDIR on a tmpfs. I note that htmltidy's test phase doesn't seem to actually do anything; could this be a bug in htmltidy that utidylib just exposes? Another possibly-relevant detail is that I'm running a hardened system. Created attachment 296615 [details]
gdb log showing context and backtrace
I've rebuilt python:2.7 and htmltidy with CFLAGS=-ggdb and FEATURES="splitdebug installsources", and produced the segfault in gdb. I attach a log showing the immediate context and the backtrace.
Created attachment 302435 [details]
Ebuild switching to a fork including patches to make tests pass
I found a fork of the project on Github, where someone took the most recent upstream sources and applied all the patches in the upstream bug tracker; after fiddling with one of the patches in the Portage tree to make it apply cleanly again (mainly whitespace issues), the tests pass. I've attach the updated ebuild here, and will upload the updated fix_tests.patch momentarily (no-docs-in-site-packages.patch needs no changes).
Created attachment 302437 [details, diff]
updated patch to apply to more recent source
This package should be last rited as it relies on an old version of htmltidy. 0.3-r2 doesn't seem to use trial anymore. |