Re: [Orbit-python-list] Re: Problem with parsing of recursive structs in IDL

[Brad C. <cha...@ar...>]

Hey all;
Thanks for the responses on this.

[I talk about a seg-fault problem caused by self-referencing
structs]

Jason:
> Yep, this certainly causes nasty things.  In fact, orbit-idl also
> segfaults on this IDL.  Maybe ORBit2's IDL compiler also has this
> problem?

Doh, thanks -- I didn't even think of looking at orbit-idl. Well now
it makes sense why I'm seeing the problem :-).

Mark McLoughlin:
>  No, ORBit2's IDL compiler has fixed this problem. If my memory
> serves me correctly, there's a fix for this in ORBit HEAD as well.

Thanks for the info. I grabbed ORBit out of CVS (the stable
revision), and it still seems to have the problem for me. Don't know
if this'll help save any time looking at it with ORBit-python.

Jason:
> BTW, you shouldn't really need to use _load_idl(). 

Well, my use case is kind of what Christian was suggesting. I'm
actually emulating stubs and skeletons (by hacking up __init__.py in
one of my modules), so I just use the _load_idl() to grab the idl
from a predefined location. It doesn't really affect my portability
in this case, because I'm already going for portability between
multiple ORBs. Thanks for the advice, though!

[My minimal test case]
Christian:
> Minimal, but 3vil. Do you have a simple test script I can integrate
> to the test-suite so we guarantee it's fixed and stays fixed 
> over versions?

Hmmm, I'm not exactly sure if this is what you want, but the
attached script will cause the seg-fault with the IDL I posted. I'm
not sure if you want seg-faulting scripts in the Test Suite though
:-)

Brad