linker.cpp line 2682

[JonathanS]

To anyone who may have had this problem and found a solution:

I was doing basic VI editing (cleaning up wires, repositioning objects, etc...) when LabVIEW crashed and told me any unsaved work would be lost.  I saved frequently, but the problem is that I can no longer access the VI I was working on.  Instead, every time I try to open it, I get an error on linker.cpp line 2682.  I have checked all of the subVI's and none of them have identical names.  Is there a solution such that I can get my VI back? 

-Jon

[Kalin_T]

Hello, Jon!

I am really sorry you are experiencing this problem. Could you please tell us what version of LabVIEW you have and what OS you are using? It would be great if you could attach the problematic VI and the error log file that was generated when you got your crash. The error log can be found in \My Documents\LabVIEW Data\lvfailurelog

Thank you!

[JonathanS]

Thank you, Kalin.  Below is the output of the error file.  I'm running LabVIEW 7.1 on Windows XP Pro SP2.  I've attached the problem file, but again, I have been unable to open it in LV 7.1, 8.0 or 8.2 since the initial crash. 




####
#Date: Mon, Mar 19, 2007 2:32:30 PM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 7.1
#AppKind: FDS



D:\lvmerc\src\source\linker\linker.cpp(2682) : DAbort: patching FP or BD with VI at bad h,o
$Id: //labview/branches/Mercury/dev/source/linker/linker.cpp#12 $
0x00A61319 - LabVIEW <unknown> + 0
0x00A611B9 - LabVIEW <unknown> + 0
0x00A5DD54 - LabVIEW <unknown> + 0
0x00A5E4A4 - LabVIEW <unknown> + 0
0x00A60526 - LabVIEW <unknown> + 0
0x00707C8C - LabVIEW <unknown> + 0
0x00A66716 - LabVIEW <unknown> + 0
0x00706B02 - LabVIEW <unknown> + 0
0x006073AE - LabVIEW <unknown> + 0
0x0070532B - LabVIEW <unknown> + 0
0x00A653E5 - LabVIEW <unknown> + 0
0x00A66911 - LabVIEW <unknown> + 0
0x009ED231 - LabVIEW <unknown> + 0
0x005ADED7 - LabVIEW <unknown> + 0
0x004B7F79 - LabVIEW <unknown> + 0


Thank you for you assistance!

-Jon

[Kalin_T]

Hello, Jon!

Thank you for posting your error log file and your VI!
I was able to open your VI just once in LabVIEW 8.2. Then I decided to download your VI to my harddrive and then run it in LV 7.1, 8.0, and 8.2. It started crashing each one of these versions of LabVIEW. Only 7.1 generated the linker.cpp error. However, mine was on a different line - linker.cpp line 2963

I asked some of my co-workers to run your VI directly from the website without explicitly saving it to their hard disk first (that's how it worked for me the first time), but they were not as lucky as I was.

This was reported to R&D (# 3YJAHGG8) for further investigation. Errors like this are very difficult to tackle as we cannot reproduce them in a way to see what part of the code causes the crash. All we know is that the VI causes LabVIEW to abort.

The best suggestion I have for you is to start from scratch and recreate your VI. I am really sorry I could not provide you with an easier solution. I wish I took a screenshot of your Block Diagram to save you some work, but I took a screenshot of the Front Panel only, thinking there was not a problem opening your VI in 8.2.

Best regards,

[Kalin_T]

here is the last crash picture as well.

[JonathanS]

Thanks again, Kalin.  I also receive the 2963 error every now and then, usually by "subverting" the usual opening method or renaming some subVI's just to see what happens.  If anything is figured out, please let me know.  Thanks!

-Jon

[amaglio]

I am having that same problem with the linker.cpp. I am just going to post the executable on the board and try to run it from there, it seems that this might provide a little bit of luck.

[Kalin_T]

Hi maggs145,

I am really sorry this happened to you. I was not able to open your VI even once. LabVIEW closed down right away. I would advise you to start over and periodically make copies of your files.

Best regards,