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.

Author jroach
Recipients brian.curtin, jroach
Date 2010-05-30.06:07:36
SpamBayes Score 0.00014333527
Marked as misclassified No
Message-id <4C0200A5.7000306@internode.on.net>
In-reply-to <1275140884.5.0.432808728378.issue8849@psf.upfronthosting.co.za>
Content
Brian,
I am an engineer who makes significant use of Python, not a computer 
professional. I hope that I communicate the right information. The 
operating system is Windows XP Professional. The problem encountered was 
that a python program invoking cvxopt, that ran perfectly well with 
Python25, crashed with Python26 and (without request) generated a 
response from Visual Studio to the effect that python.exe encountered an 
access violation writing location 0x9b0b80c8. (The full message was 
'Unhandled exception  at 0x01de5607 in python.exe:0xC0000005: Access  
violation writing location 0x9b0b80c8. The c-code segment displayed by 
the debugger was (file: crt0dat.c):
  /*
         * walk the table of function pointers from the bottom up, until
         * the end is encountered.  Do not skip the first entry.  The 
initial
         * value of pfbegin points to the first valid entry.  Do not try to
         * execute what pfend points to.  Only entries before pfend are 
valid.
         */
        while ( pfbegin < pfend )
        {
            /*
             * if current table entry is non-NULL, call thru it.
             */
            if ( *pfbegin != NULL )
                (**pfbegin)();
            ++pfbegin;
        }
}

/***
* static int  _initterm_e(_PIFV * pfbegin, _PIFV * pfend) - call entries in
*       function pointer table, return error code on any failure
*
*Purpose:
*       Walk a table of function pointers in the same way as _initterm, but
*       here the functions return an error code.  If an error is 
returned, it
*       will be a nonzero value equal to one of the _RT_* codes.
*
*Entry:
The call stack line was: >    msvcr90.dll!_initterm(void (void)* * 
pfbegin=0x00000002, void (void)* * pfend=0x00993148)  Line 903    C
I do not have the necessary knowledge to interpret these data.
This Python26 problem occurs with every execution under both Idle and 
Editra.

jroach
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue8849>
> _______________________________________
>
>
History
Date User Action Args
2010-05-30 06:07:41jroachsetrecipients: + jroach, brian.curtin
2010-05-30 06:07:39jroachlinkissue8849 messages
2010-05-30 06:07:36jroachcreate