SourceForge has been redesigned. Learn more.
Close

#909 Bug in ForwardMessage

v4.0.1
closed
nobody
APIs (66)
none
3
2013-11-21
2010-04-30
No

Environments:
Fedora 12 32-bit Linux running 4.0.1 rc1
Fedora 12 64-bit Linux running 4.0.1 rc1
Ubuntu 64-bit Linux running 4.0.1 rc1

There is a difference between the 32-bit and the 64-bit versions of the ForwardMessage API. On a 32-bit system the code works as expected but on the 64-bit systems listed above the same code produces a seg fault due to a NULL pointer. This can be confirmed by compiling RexxGTK on any 64-bit system and running any of the test programs that invoke the signal_connect method on any GTK object.

The specific C++ code that causes the problems is

ForwardMessage(NULLOBJECT, NULL, super, NULLOBJECT);

This code is invoked when the signal being connected is implemented by the super class of the ooRexx object. It is used in almost all GTK object implementation in RexxGTK.

Discussion

  • Rick McGuire

    Rick McGuire - 2013-11-20

    David, I believe this was resolved, correct?

     
  • David Ashley

    David Ashley - 2013-11-21

    I believe this was resolved long ago.

     
  • Rick McGuire

    Rick McGuire - 2013-11-21
    • status: open --> closed
    • Pending work items: --> none
     
  • Rick McGuire

    Rick McGuire - 2013-11-21

    This doesn't appear to be a real problem.

     

Anonymous
Anonymous

Cancel  Add attachments