[issue12181] SIGBUS error on OpenBSD (sparc64)

2011-05-27 Thread Nicholas Marriott
Nicholas Marriott added the comment: Well "they do it that way" is not a justification that necessarily works for OpenBSD :-). I'll see if I can come up with a diff to fix this in Python. Not this weekend though, maybe next week. Unless Remi do you wa

[issue12181] SIGBUS error on OpenBSD (sparc64)

2011-05-27 Thread Nicholas Marriott
Nicholas Marriott added the comment: Not that I'm unsympathetic but this is really only a concern if you depend on the internal structure layout and I think if you do that, you need to take account of differences between platforms. We don't guarantee we aren't going to ch

[issue12181] SIGBUS error on OpenBSD (sparc64)

2011-05-27 Thread Nicholas Marriott
Nicholas Marriott added the comment: Hi The second one is correct - OpenBSD -current has this in event.h: struct kevent { u_int ident; /* identifier for this event */ short filter; /* filter for event */ u_short flags

[issue12181] SIGBUS error on OpenBSD (sparc64)

2011-05-26 Thread Nicholas Marriott
Nicholas Marriott added the comment: To follow up a little - I'm afraid that you should not depend on the internal layout of structures like this. We clearly document the kevent structure in kevent(2), and of course beyond that it is of course dependent on C padding rules. It isn&#x

[issue12181] SIGBUS error on OpenBSD (sparc64)

2011-05-26 Thread Nicholas Marriott
Nicholas Marriott added the comment: Hi This is not an OpenBSD bug. kqueue is not standardized. There is no reason for the ident member to be uintptr_t over u_int - either is valid, and so far I don't see any reason for us to try and change it. -- nosy:

[issue1471] ioctl request argument broken on 64-bit OpenBSD or OS X

2008-07-20 Thread Nicholas Marriott
Nicholas Marriott <[EMAIL PROTECTED]> added the comment: I was going to test this on sparc64 (I no longer have access to amd64) but I've been busy/on holiday, I'll try to do it this week. ___ Python tracker <[EMAIL PROTECTED]> &

[issue1471] ioctl doesn't work properly on 64-bit OpenBSD

2008-03-17 Thread Nicholas Marriott
Nicholas Marriott <[EMAIL PROTECTED]> added the comment: It's not the return value, it's the request argument (second argument). I thought SUSv3 had it as an int, but looking again its ioctl seems to be a) optional and b) all about STREAMS, so I don't think it applies: htt

[issue1471] ioctl doesn't work properly on 64-bit OpenBSD

2007-11-20 Thread Nicholas Marriott
Nicholas Marriott added the comment: Okay, looks like my guess was correct. The diff at the end of this mail makes it work on OpenBSD/amd64 and it continues to work on i386, but it will probably break Linux (due to the problem it was working around mentioned in the comment at the beginning

[issue1471] ioctl doesn't work properly on 64-bit OpenBSD

2007-11-20 Thread Nicholas Marriott
Nicholas Marriott added the comment: I can also reproduce this on OpenBSD/amd64 and was one of the people who discussed it with the submitter before he created this report. > So what's the definition of struct winsize on these systems? The definition of struct winsize on both 32-bit an