SystemError: ... cellobject.c:22: bad argument to internal ?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • robert

    #1

    SystemError: ... cellobject.c:22: bad argument to internal ?

    From the trace of a 2.3.5 software i got:

    \'SystemError:
    C:\\\\sf\\\\pyt hon\\\\dist23\\ \\src\\\\Object s\\\\cellobject .c:22: bad
    argument to internal
    function\\n\']


    from the middle of normal function / or its call. What is this?

    There is:



    but seems to be something else. There is no dynamic addition of
    class-method. But the last function called is a callback function in
    3rd level inner function of class method like:

    class X:
    def a():
    def b():
    ...
    def c():... # breaks with systemerror
    schedule_callba ck(c) # -> upon Windows WM_TIMER event
    ...


    Will there be another bug-fix release of Python 2.3 ?

    -robert


  • nnorwitz@gmail.com

    #2
    Re: SystemError: ... cellobject.c:22 : bad argument to internal ?

    robert wrote:[color=blue]
    > From the trace of a 2.3.5 software i got:
    >
    > \'SystemError:
    > C:\\\\sf\\\\pyt hon\\\\dist23\\ \\src\\\\Object s\\\\cellobject .c:22: bad
    > argument to internal
    > function\\n\'][/color]

    ....
    [color=blue]
    > Will there be another bug-fix release of Python 2.3 ?[/color]

    No, is this still a problem in 2.4? 2.4.4 is planned to be released
    this summer. Can you post the entire code (that doesn't reference
    anything outside the stdlib) that causes this problem?

    n

    Comment

    • robert

      #3
      Re: SystemError: ... cellobject.c:22 : bad argument to internal ?

      nnorwitz@gmail. com wrote:[color=blue]
      > robert wrote:
      >[color=green]
      >>From the trace of a 2.3.5 software i got:
      >>
      >>\'SystemError :
      >>C:\\\\sf\\\\p ython\\\\dist23 \\\\src\\\\Obje cts\\\\cellobje ct.c:22: bad
      >>argument to internal
      >>function\\n \'][/color]
      >
      >
      > ...
      >
      >[color=green]
      >>Will there be another bug-fix release of Python 2.3 ?[/color]
      >
      >
      > No, is this still a problem in 2.4? 2.4.4 is planned to be released[/color]

      ( Am bound to py2.3 for this app - as py2.4 more than doubled
      distributable app sizes with MSVCRTL71, CJK codecs in core etc... )
      [color=blue]
      > this summer. Can you post the entire code (that doesn't reference
      > anything outside the stdlib) that causes this problem?
      >[/color]

      Solved - no Python error.

      The bug turned out to be a refcount bug in PythonWin's
      win32ui.HookMes sage internals: the Python callback upon WM_TIMER didn't
      INCREF the called function object itself. When the function removed
      itself from the hook list (indirectly), the executing functions
      closure/cells.. were recycled while the function was still executing.

      https://sourceforge.net/tracker/inde...18&atid=551954

      -robert

      Comment

      Working...