New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pointer aliasing causes core dump, with workaround #42918
Comments
When building 2.3.3 on Solaris using Studio 11 and I was able to simplify the code to invoke the problem class C1(object):
def __new__(cls):
return super(C1, cls).__new__(cls)
a = C1() ==== I tracked the problem to super_init() in The local variable "obj" is of type "PyObject *" and A workaround is to cast one of the pointers to the What I suspect needs to be done as a more global fix is |
Logged In: YES I have the vague impression that Python's code doesn't Assigning to Tim Peters, who will know if the |
Logged In: YES There is no reason why the source code for Python cannot The only reason to use a switch like GCC's |
Logged In: YES Yes, Python must be compiled with -fno-strict-aliasing (or No, that's not going to change before Python 3000 (if even Note that Python doesn't much care about C99. It was That said, I don't see anything to object to in adding |
Logged In: YES It doesn't matter which standard is used, C99 or C89, the An object is being accessed through two different aggregate (Actually, C99 is slightly looser than C89 since it allows |
Logged In: YES Sorry, but it still doesn't really matter what any version |
Logged In: YES I wasn't demanding the bug be fixed in the present source I was just trying to clarify that the trick is an invalid |
Logged In: YES Ah, OK, and I have no argument with that. Well ;-), I'd |
Should we fix the general issue in Python 3.0 now that Python 3.0 is |
Can a core dev please look at this now that we're at 3.2 alapha, thanks. Or has it already been fixed? |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: