This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Solaris and Python/pykota
Type: Stage:
Components: Interpreter Core Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: loewis, mwh, ormsbyka
Priority: normal Keywords:

Created on 2005-03-04 04:44 by ormsbyka, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
pdlanalyzer.py ormsbyka, 2005-03-04 04:44 pdlanalyzer from pykota
Messages (5)
msg24467 - (view) Author: Kelly Ormsby (ormsbyka) Date: 2005-03-04 04:44
I have a Solaris 9 system that I have installed Python
2.4 on with the following modules:
egenix-mx-base 2.0.6
jaxml3.0.1
python-snmp 3.4.3
psyco 1.4
reportlab 1.20
and postgresql 3.6.1
net-snmp 5.2.1
which are all required by pykota (a print quota
management system)

I am having the issue that when pykota is plugged in to
my cups system, and I try to print, the print job is
put on hold and printing to that printer is stopped.

I tried running the pykota software from the command
line to see what is causing the problem and from what I
(and Jerome Alet from librelogiciel.com) can work out
it is a problem with the solaris build of python.

I have used gcc 3.3 and binutils 2.14 to build python.

The following is what happens when I try running from
the command line:

#python /usr/local/pykota/pykota/pdlanalyzer.py --debug
~kelly/align.ps
/home/staff/kelly/align.ps is a PostScript file
Bus error (core dumped)
# pkpgcounter --debug ~kelly/align.ps
/home/staff/kelly/align.ps is a PostScript file
Bus error (core dumped) 

I have attached the pdlanalyzer.py file for you to look at.

Please let me know what I should do.
msg24468 - (view) Author: Michael Hudson (mwh) (Python committer) Date: 2005-03-04 10:34
Logged In: YES 
user_id=6656

Well, that's kind of a large module for us to pick at...

Does it only crash on certain postscript files?  Can you run
it under a debugger/analyze a core file to see where it's
crashing?  Does it only crash with 2.4.0 -- can you try
2.3/release24-maint from CVS/CVS HEAD?

It doesn't crash for me with any of the ps files I happen to
have lying around with release24-maint head (what will soon
be 2.4.1) on linux.  I don't have a version 2.4.0 lying
around though.
msg24469 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2005-03-23 20:56
Logged In: YES 
user_id=21627

When you say Solaris, it is not really clear what you mean: x86 or 
SPARC? I very much doubt that psyco works on SPARC.
msg24470 - (view) Author: Kelly Ormsby (ormsbyka) Date: 2005-03-24 00:23
Logged In: YES 
user_id=505289

It is sparc solaris (sorry I always forget solaris runs on
x86 :)

So psyco won't work on sparc architecture? Well that sucks.
I was in the process of freshly installing a machine to try
it out on. I guess I won't bother :(

Thanks for your help!
msg24471 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2005-03-24 21:19
Logged In: YES 
user_id=21627

psyco is a just-in-time compiler, and it only supports x86. However, I very 
much doubt that it is *really* needed by that application. As it doesn't do 
anything but JIT, you should be able to take it out fairly easily.

Closing as third-party bug.
History
Date User Action Args
2022-04-11 14:56:10adminsetgithub: 41652
2005-03-04 04:44:09ormsbykacreate