freebsd: error when running pytags

Bug #571979 reported by jtbm on 2010-04-30
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pytagsfs
Medium
Unassigned

Bug Description

FreeBSD 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1

Traceback (most recent call last):
  File "/usr/local/lib/python2.6/site-packages/sclapp/main.py", line 181, in main
    announce_signals = announce_signals
  File "/usr/local/lib/python2.6/site-packages/sclapp/signals.py", line 295, in enableSignalHandling
    _pushCurrentSignalMapping()
  File "/usr/local/lib/python2.6/site-packages/sclapp/signals.py", line 123, in _pushCurrentSignalMapping
    d[signum] = signal.getsignal(signum)
ValueError: signal number out of range

Something bad happened, and is most likely a bug.
Please file a bug report to the author.
Include the error message(s) printed here.
exiting with status 255

I am able to use pytagsfs, but not pytags

Forest Bond (forest-bond) wrote :

Thanks for the report.

Looks like the Python signal module contents are different than I'd expect them to be (it appears to define signals that are not supported by the underlying system). I would like to fix this, but I will probably do so when migrating from sclapp to sclapp2 (a work in progress). Unfortunately, this will probably not happen for a few months as time is currently limited.

I'll attach a patch that disables sclapp's signal handling for pytags. You can use this work around until a proper fix is ready.

Thanks,
Forest

Forest Bond (forest-bond) wrote :
Changed in pytagsfs:
importance: Undecided → Medium
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers