LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

cvi 7.0 crashes in debug mode

I've just installed cvi 7.0 and my application on a new PC. It runs absolutely fine in release mode, but in debug mode cvi crashes before the first statement in my program. I installed cvi version 6.0 and this works absolutely fine, but I don't want to develop this project using an old version of cvi.
The PC is a Dual Athlon processor machine running XP. We have a similar spec. PC which does not have the problem. Lengthy investigations have not revealed any faults with the PC, and all other software runs with no problems.
0 Kudos
Message 1 of 16
(5,464 Views)
Hello,

It's Pete from National Instruments technical support department here. I've been looking into this problem for you and cannot find any records of something like this happening before. Therefore, I need to ask a few questions in order to try and narrow down the problem a bit.

Are the two PC's exactly the same? There must be something different in the setup which is causing this difference in performance, either that or there is some dodgy memory on one PC, which CVI is trying to access when you run it in debug mode - or something like that. I would have thought this to be very unlikely.

One thing to try if possible might be to take a ghost image of the working PC and put that on the dodgy PC. We use this technique here to enable us to quickly an
d easily create a clean machine with just the required software installed and nothing else that could mess things up.

You say that you have installed your application on the PC that is not working. I assume you are running this same application on the PC that is working. Which PC was the application built on? Are all drivers required on both machines?

Basically I am just trying to make sure that the setup between the two machines is identical in order to try and eliminate as many possibilities as we can to start with.

Let me know the results of this.

Best regards,

Peter H.
Applications Engineer.
National Instruments.
Message 2 of 16
(5,460 Views)
Hi Pete,

Thanks for answering. I think that you are right and it must be something to do with the rogue PC, but it's odd as it only affects cvi v7.0.

The only differences in the two PCs are:-
A has two HDDs arranged as a striped RAID
B has a single HDD
A has 2.5 Gb RAM while B has 1.5 Gb RAM
Everything else:- motherboard, processors, network board, graphics board, firewire board are the same.
A is the one that works OK.

Unfortunately we can't ghost the working PC due to the RAID arrangement.

I have an application which uses no external drivers.
It will build and run on A in debug mode.
It will build on B and can be run (Ctrl+F5), but when you press the green arrow, (Shift+F5), to debug this or any program cvi crashes.

Regards
Rosalind
Locke
0 Kudos
Message 3 of 16
(5,460 Views)
Hi Rosalind,

Sorry for the delayed response, we've been very busy in the department this week.

Anyway, have you tried uninstalling and reinstalling CVI. I can send you a customized version of MSIBlast if you want which will allow you to completely uninstall all NI software on your machine (you may have to go in to Add/Remover programs as well just to clean up a couple of files). This will allow you to start from a fresh machine and hopefully this will install correctly.

I know this sounds a bit drastic but would it be possible to try and run the computer with certain parts swapped out to see if the problem still occurs. For instance, change the RAM over to see if you have a bad bit of RAM.

Hopefully this won't be neccesary as the prob
lem may be solved by reinstalling the software.

Best regards,

Peter H,
Applications Engineer,
National Instruments.
0 Kudos
Message 4 of 16
(5,460 Views)
Hi Peter,

Thanks for your suggestions. I did try uninstalling and reinstalling cvi afew times, but I haven't used MSIBlast. Maybe that could achieve a cleaner uninstall for me. Can you email it to me at locke@gci.ac.uk

I'll also try swapping the memory chips as well though it did pass MEMTEST OK.

Many thanks
Ros Locke
0 Kudos
Message 5 of 16
(5,461 Views)
I have this probelm with CVI 7.1.1. I have installed the latest patch but CVI still kills the app before the first line in main() is run and then kills itself.  If rerun CVI and run in Release mode everything is fine.  I haven't had any memory problems so I don't think I'm hitting bad memory.  Was there any resolution to this issue?  Maybe in another thread?

I did change my "Debug Capable" program structure from everything being in main(), except for a few calls to a .h file I use for everything, to a more managable .h/.c structure.  I could see how I might be allocating memory wrong or making some crucial C mistake but then why does the program work in Release?  Maybe there is some kind of verification that Debug does on poniters that is causing trouble?  Files are all over the place now so I could see how there could be issues.  CVI is usually so good though at telling me where to start looking for the problem if not telling me exactly how to fix it. 

Grant


Grant M. Johnson
Project Engineer
LECO Corporation
0 Kudos
Message 6 of 16
(5,321 Views)
I started commenting stuff out until I could build successfully in Debug mode.  Then I started putting stuff back and ended up putting everything back and it works now.

I had tried setting my Options->Build Options->Debug level to "No runtime checking" and it didn't fix anything.  Then I remembered after I put everything back that runtime checking was still disabled.  I set the Debug Level back to Standard and it still works. 

All this just to say I really don't have anything for you to go on.  I did try deleteing all my debug files from my program directory and then rebuilding just to try and make sure I had a clean install but that didn't seem to help.

Don't worry about replying if you don't want.

Grant


Grant M. Johnson
Project Engineer
LECO Corporation
0 Kudos
Message 7 of 16
(5,310 Views)

Hi,

I have kind of the same problem, but worse !

I have XP Pro, and the .Net Framework and development studio installed;

I can't get my progs to run either in debug or release; even if I try to run old release that were compiled before (I'm not sure if it's before the framework installation, or move to XP, or both), the progrm crash.

"Fatal Runtime Error, unknown source position, thread ID 0x00000C24, a non-debugable thread caused a 'General protection' fault at address 00000000.

 

I tried removing all NI software with windows uninstall software, then reinstalling it, but it chnges nothing.

If you send me the remover you mentionned, I can try it (jbentz@barrette-chapais.qc.ca), otherwise, do you have any idea ?

 

Thank you

0 Kudos
Message 8 of 16
(5,272 Views)
Hello

I have the same problem.  All was fine and I started to add more code.  But know it doesn't works.  It crashes before entering the main function (i tried a breakpoint).

The message is:
Unknown source position, thread id <an hexa number>.  A non-debuggable thread caused a 'General protection' fault at address <an other number>.

It uses an external dll.  Maybe is this fault due to a recompilation??  I don't know the problable causes to start the investigation (I can't debug!), so any idea will be appreciated.

I'm using CVI 6.0 in a w2000 computer.

Thank you
Carlos Arcediano del Amo
0 Kudos
Message 9 of 16
(5,189 Views)
Hi,
 
I have a similar problem. I modify one program in my work, but It does not work in debbug mode, no errors, it just stops. The break points are ignored. Do anyone know if there is any missing ?
 
I'm using CVI7.0, Xindows XP SP2.
 
Thanks
0 Kudos
Message 10 of 16
(4,278 Views)