[ python-Bugs-1112949 ] ioctl has problems on 64 bit machines
Bugs item #1112949, was opened at 2005-01-31 05:55
Message generated for change (Comment added) made by birkenfeld
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1112949&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Platform-specific
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Stephen Norris (stephennorris)
Assigned to: Nobody/Anonymous (nobody)
Summary: ioctl has problems on 64 bit machines
Initial Comment:
fcntly.ioctl takes an int as the second argument. If
the value passed is a large 32 bit quantity (0x80046601
for example - EXT2_IOC_GETFLAGS) then I get:
Traceback (most recent call last):
File "CommSecure-CVS/Operations/checkSpace.py", line
73, in ?
main(sys.argv[1:])
File "CommSecure-CVS/Operations/checkSpace.py", line
25, in main
os.path.walk(file, doDirectory, total)
File "/usr/lib64/python2.3/posixpath.py", line 282,
in walk
func(arg, top, names)
File "CommSecure-CVS/Operations/checkSpace.py", line
61, in doDirectory
flags = fcntl.ioctl(fd, EXT3_IOC_GETFLAGS, "")
OverflowError: signed integer is greater than maximum
My _guess_ here is that the code is checking against 32
bit quantities rather than 64 bit when converting to
the C data type?
Platform is Linux, Fedora Core 3 on AMD Opteron.
--
>Comment By: Reinhold Birkenfeld (birkenfeld)
Date: 2005-07-28 09:06
Message:
Logged In: YES
user_id=1188172
Should be fixed wrt patch 1231069.
--
Comment By: Chris Lawrence (lordsutch)
Date: 2005-07-21 03:11
Message:
Logged In: YES
user_id=6757
The problem seems to be that Python integers are "long int,"
while the type expected by ioctl(2) is "unsigned long int"
(on AMD64, at least).
My hackish workaround is to coerce the ioctl number to a
signed quantity:
op = struct.unpack('i', struct.pack('I', op))[0]
Once it gets into the C code, the signed quantity is then
coerced back to unsigned long int by the ioctl call (after
an intermediate stop as (signed) int).
Probably, the correct course of action here is to figure out
what type ioctl(2) uses on a particular architecture and
adjust the PyArgs_ParseTuple() call and the type of "op"
accordingly.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1112949&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1246900 ] failure to build RPM on rhel 3
Bugs item #1246900, was opened at 2005-07-28 12:14
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1246900&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Patrick Wagstrom (pridkett)
Assigned to: Nobody/Anonymous (nobody)
Summary: failure to build RPM on rhel 3
Initial Comment:
This is on RHEL 3 AS (Taroon update 5) on a dual
processor x86_64 machine
Attempting to build the RPM from Python.org fails with
a very non-descript error message:
+ mv -f idle idle2.4
+ echo '#!/usr/bin/env python2.4'
+ echo 'import os, sys'
+ echo 'os.execvp("/usr/bin/python2.4",
["/usr/bin/python2.4",
"/usr/lib/python2.4/idlelib/idle.py"] + sys.argv[1:])'
+ echo 'print "Failed to exec Idle"'
+ echo 'sys.exit(1)'
+ chmod 755 /var/tmp/python2.4-2.4.1-root/usr/bin/idle2.4
+ cp -a Tools
/var/tmp/python2.4-2.4.1-root/usr/lib64/python2.4
+ rm -f mainpkg.files
+ find
/var/tmp/python2.4-2.4.1-root/usr/lib64/python2.4/lib-dynload
-type f
+ sed 's|^/var/tmp/python2.4-2.4.1-root|/|'
+ grep -v -e '_tkinter.so$'
error: Bad exit status from /var/tmp/rpm-tmp.97009
(%install)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.97009 (%install)
So, thinking that it might be something related to
tkinter and idel, I tried not building those, but it
still fails to complete. It appears that the problem
is that nothing is getting put in /usr/lib64 and
everything is getting put in /usr/lib.
Attempts were made at hacking the spec file to pass
--libdir=/usr/lib64 --exec-prefix=/usr to configure and
still have the problem that it doesn't put anything in
/usr/lib64 even though the spec file, and common logic,
would expect there to be files in /usr/lib64.
I was able to compile Python 2.4 just fine on the
machine and install it, but still it did not have
anything in /usr/lib64/python2.4, which is where the
architecture specific files should be.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1246900&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1244864 ] Segfault in Python interpreter 2.3.5
Bugs item #1244864, was opened at 2005-07-25 19:53 Message generated for change (Comment added) made by tjreedy You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1244864&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Python 2.3 Status: Open Resolution: None Priority: 5 Submitted By: Evil Mr Henry (evilmrhenry) Assigned to: Nobody/Anonymous (nobody) Summary: Segfault in Python interpreter 2.3.5 Initial Comment: Linux, Debian Testing, with Bash shell. If I type "python" at the bash prompt to start the interpreter, then hit the up arrow key (the previous command key), Python segfaults. This only occurs if there are no previous commands in the queue. -- >Comment By: Terry J. Reedy (tjreedy) Date: 2005-07-29 01:40 Message: Logged In: YES user_id=593130 Does this happen with 2.4.1? There will probably not be a 2.3.6. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1244864&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1244864 ] Segfault in Python interpreter 2.3.5
Bugs item #1244864, was opened at 2005-07-25 23:53 Message generated for change (Comment added) made by evilmrhenry You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1244864&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Python 2.3 Status: Open Resolution: None Priority: 5 Submitted By: Evil Mr Henry (evilmrhenry) Assigned to: Nobody/Anonymous (nobody) Summary: Segfault in Python interpreter 2.3.5 Initial Comment: Linux, Debian Testing, with Bash shell. If I type "python" at the bash prompt to start the interpreter, then hit the up arrow key (the previous command key), Python segfaults. This only occurs if there are no previous commands in the queue. -- >Comment By: Evil Mr Henry (evilmrhenry) Date: 2005-07-29 05:52 Message: Logged In: YES user_id=1052361 Does not occur with 2.4.1. -- Comment By: Terry J. Reedy (tjreedy) Date: 2005-07-29 05:40 Message: Logged In: YES user_id=593130 Does this happen with 2.4.1? There will probably not be a 2.3.6. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1244864&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
