Actions
Forum Thread Details
  • Replies 16 replies
  • Subscribers 178 subscribers
  • Views 1218 views
  • Users 0 members are here
Related

Reference to uninitialize d object variable [5.11]

autodeskguest

Yesterday I was fiddling around with an ulp to create a more complete FATF

file. Needless to say, it had 'some' typos... :roll:

 

When it finally started, I got (in the midst of processing) this message:

Reference to uninitialized object variable.

The line referred to is part of a loop that had already executed several

times without a problem, so I am at a loss here. To be more precise: the

processing of contact references on a net.

The design checks OK in both ERC and DRC, apart from some minor issues with

angles and such.

 

To check the data, I started another ulp (attached) on the same board to

find the culprit and got the same error message (at line 253), again while

processing contact references on that same net...

 

What causes this message, and more importantly, how do I solve it?

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

 

Parents

  • Thanks for the replies so far, it was both helpful and giving insight.

     

    No amount of cutting/pasting would resolve the issue, even a complete(?)

    removal of the offending net and connected parts did not help. Apparently

    there remained some sort of a stub...

     

    The check that Morten suggested circumvents the problem: no more crash.

    It generates however an 'empty' net reference that will most likely cause

    problems in the FATF output of the original ulp. But with the problem now

    identified, that is an easy fixable problem.

     

    I'd rather fix the source of the mayhem though, but the binary pcb format

    presents a major hurdle in this endeavour.

    Oh well, just another reason to upgrade I guess...

    --

    Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

     

  • in reply to autodeskguest

    On 25.04.2016 14:26, Leo wrote:

    Thanks for the replies so far, it was both helpful and giving insight.

     

    No amount of cutting/pasting would resolve the issue, even a complete(?)

    removal of the offending net and connected parts did not help. Apparently

    there remained some sort of a stub...

     

    The check that Morten suggested circumvents the problem: no more crash.

    It generates however an 'empty' net reference that will most likely cause

    problems in the FATF output of the original ulp. But with the problem now

    identified, that is an easy fixable problem.

     

    I'd rather fix the source of the mayhem though, but the binary pcb format

    presents a major hurdle in this endeavour.

    Oh well, just another reason to upgrade I guess...

     

     

    The source of the problem is here: 5.11 image Time to upgrade?

     

    I made a script to remove null objects in 6.x, but cant remember if the

    clr/setgroup commands worked in 5.x.. Prob not. Anyway, I attach my script.

     

    You may find some very old threads written by me how to get rid of them

    them in 5.x... But my memory has faded.. I think it may involve some

    manual operations, like routing a dummy net to the contact and delete it

    again.

     

     

     

     

  • in reply to autodeskguest

    The posted ulp did not function (as expected).

    I just added the conditions where needed and got on with it...

    Update will be done, but not in the near future due to a very busy

    schedule.

    --

    Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

     

  • in reply to autodeskguest

    The posted ulp did not function (as expected).

    I just added the conditions where needed and got on with it...

    Update will be done, but not in the near future due to a very busy

    schedule.

    --

    Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

     

  • in reply to autodeskguest

    The posted ulp did not function (as expected).

    I just added the conditions where needed and got on with it...

    Update will be done, but not in the near future due to a very busy

    schedule.

    --

    Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

     

  • in reply to autodeskguest

    On 28.04.2016 17:20, Leo wrote:

    The posted ulp did not function (as expected).

    I just added the conditions where needed and got on with it...

    Update will be done, but not in the near future due to a very busy

    schedule.

     

     

    Off topic, but I stopped worrying about upgrades performing and rather

    use whatever is latest. Even beta's. The reason is that I always

    generate IPC netlist and check the final gerbers against the netlist

    using a 3rd party tool. This gives me a very good confidence that the

    latest Eagle will not cause any non detectable issues.

     

    Leaving 5.x behind does also give you xml source files wich are nicer to

    tweak and diff.

     

     

  • in reply to autodeskguest

    On 28.04.2016 17:20, Leo wrote:

    The posted ulp did not function (as expected).

    I just added the conditions where needed and got on with it...

    Update will be done, but not in the near future due to a very busy

    schedule.

     

     

    Off topic, but I stopped worrying about upgrades performing and rather

    use whatever is latest. Even beta's. The reason is that I always

    generate IPC netlist and check the final gerbers against the netlist

    using a 3rd party tool. This gives me a very good confidence that the

    latest Eagle will not cause any non detectable issues.

     

    Leaving 5.x behind does also give you xml source files wich are nicer to

    tweak and diff.

     

     

Reply
  • in reply to autodeskguest

    On 28.04.2016 17:20, Leo wrote:

    The posted ulp did not function (as expected).

    I just added the conditions where needed and got on with it...

    Update will be done, but not in the near future due to a very busy

    schedule.

     

     

    Off topic, but I stopped worrying about upgrades performing and rather

    use whatever is latest. Even beta's. The reason is that I always

    generate IPC netlist and check the final gerbers against the netlist

    using a 3rd party tool. This gives me a very good confidence that the

    latest Eagle will not cause any non detectable issues.

     

    Leaving 5.x behind does also give you xml source files wich are nicer to

    tweak and diff.

     

     

Children
No Data