On Sep 24, 11:05 am, "Aaron \"Castironpi\" Brady"
<[EMAIL PROTECTED]> wrote:
> On Sep 24, 6:30 am, Nick Craig-Wood <[EMAIL PROTECTED]> wrote:
>
>
>
> > [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > >  my code:
> > >  main.cpp
> > >  #include <Python.h>
>
> > >  int main(int argc, char **argv)
> > >  {
> > >  Py_Initialize();
>
> > >  FILE *file_1 = fopen("a2l_reader.py","r+");
> > >  PyRun_SimpleFile(file_1,"a2l_reader.py");
>
> > >  Py_Finalize();
> > >  }
>
> > >  compile under windows using MinGW:
> > >  g++ main.cpp libpython25.a -o a
>
> > >  no error was found. But when I run a.exe the program just crashes.
>
> > >  What should I do?
>
> > Run it under gdb (which should have come with MinGW).
>
> > Check that you actually opened the file, ie file_1 != 0.
>
> > This might be relevant
>
> >  http://effbot.org/pyfaq/pyrun-simplefile-crashes-on-windows-but-not-o...
>
> > --
> > Nick Craig-Wood <[EMAIL PROTECTED]> --http://www.craig-wood.com/nick
>
> There's a workaround.
>
> filename = "Entire path of the python file";
> PyObject* PyFileObject = PyFile_FromString(filename, "r");
> PyRun_SimpleFile(PyFile_AsFile(PyFileObject), filename);
> // decref PyFileObject
>
> http://mail.python.org/pipermail/python-list/2007-March/431725.htmlhttp://python-forum.org/pythonforum/viewtopic.php?f=15&t=1554&p=6567

Just to follow up-- The links say that the crash comes from opening a
file with two different versions of a library.  Would it be possible
to get an API entry point to the version the build uses?

It does use the 'fopen' function by name, but not the same version.
And creating the entire object just to get its f_fp field is really
long.
--
http://mail.python.org/mailman/listinfo/python-list

Reply via email to