Spectrogram Graph Curser Crashes Labview

I was wondering if anybody else have this happen to them. I'm trying to set the location of the cursor on a spectrogram (intensity graph) (the x value), and it crashes Labview. I tried compiling to a .exe, and it still does the same on another computer.
Message Edited by d1sturbanc3 on 02-19-2009 11:33 AM
Message Edited by d1sturbanc3 on 02-19-2009 11:33 AM

what version of LV? what OS? can you post a subset of your code that demonstrates the problem?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Similar Messages

XYGraph Cursor legend bug instantly crashes LabView 2012

Hi!
I am just facing a very annoying bug.
Please find my example VI attached, I would like to know wheather you can confirm the bug? Run the VI if you wish to see some curve (actually the bug appears even if you do not put any data on the graph, if you do, just the same) and after that try to click on the cursor legend vertical scrollbar to scroll up or down to see the cursor names.
It instantly crashes my LabView 2012 Full version: 12.0.1f2 (32-bit). This XYGraph always crashes LabView... I cannot go on with my project, now I will just try to bypass the error, I will try to delete the cursors, and add them again...
Anyhow, very strange and annoying behaviour...
Anyone could repeat the same bug?
Thanks for support!
Solved!
Go to Solution.
Attachments:
XYGraph_bug_test1.vi ‏149 KB

hello,
please find attached my example VI, where I would like to programmatically set the label position of a cursor. Why my code does create at every run a new cursor with the same name?
thanks!
Attachments:
cursor_offset_label_via_propertynode.vi ‏12 KB

How to let the user define the colors for each plots in the graph (I use LabVIEW 7)?

How to let the user define the colors for each plots in the graph (I
use LabVIEW 7)?

Hi,
Take a look at this example, it uses property nodes to select tha
active plot and then changes the color of that plot.
If you want to make the number of plots dynamic you could use a for
loop and an array of color boxes.
I hope this helps.
Regards,
Juan Carlos
N.I.
Attachments:
Changing_plot_color.vi ‏38 KB

How to generate an s-curve graph/chart in labview

I would like to generate my s-curve shape in a visible graph in a labview vi. Are there any quick/dirty vi's that can take position, accel/decel, vel and jerk value, and plot this into a time graph? Something akin Motion Assistant...
I am able to construct a trapazoid graph using basic algebra within lab view, but cannot find a good formula to compute an s-curve. I am familiar with converting the jerk value to actual counts/s^3, but from there on, I do not know how NI-Motion calculates to accel, decel and velocity times. Thanks.

Hello,
What versions of LabVIEW and Motion Assistant are you using? Motion Assistant 1.2 exposes its API to LabVIEW and these functions can be accessed by opening LabVIEW and navigating to All Functions >> NI Measurements >> Motion >> Motion Assistant. Using these VIs, you can set up a move and use the Get Move Profile VI to obtain an array of points for the velocity profile.
Beyond this method, there is no straightforward way to obtain those datapoints.
If you have any questions about this method, please let me know.
Regards,
Scott R.
Applications Engineer
National Instruments

Save for previous version 8.5 to 8.2 generates code that crashes Labview (uses classes)

Hello,
I'm working on some java style interfaces for labview for hot swapping of instrumentation for design patterns. When I try to port this code, developed on Labview 8.5 back to labview 8.2, the code it generates crashes labview (both 8.5 and 8.2).
Included is a small snipet of the work that demonstrates this behavior.
It includes to classes:
untitledProject1 - the containing project (version 8.5)
FunctionGeneratorI - Similar to a Java style interface (A class with all Dynamic VI's with no useful functionality)
FunctionGenerator33220a - An intended implementation of Function generator (only a few functions implemented)
and a folder "labview8_2Distribution"
Which contains the port of the 8.5 code to 8.2.
To recreate the error:
A.
1. Open "labview8_2Distribution\Users\Laptop\Desktop\object\Untitled Project 1" (8.2 save)
2. Verify it crashes labview 8.5 and labview 8.2.
3. Watch labview crash?
B.
1. Open the "Untitled project 1" in the root directory. (Using labview 8.5)
2. Save the project as a labview 8.2 type.
3. Try to open the saved version with 8.5 and 8.2.
4. Watch labview crash?
Greg Sonnenfeld
Attachments:
error.zip ‏885 KB

Hello Karunya,
In regards to your questions:
>Can you post your code? Have you tested this by creating another project?
Do you have an xcontrols in your projects? Do you have typedefs? Do you
have a LVOOP constant on your block diagram? Are you also using Classes?
I cannot post the cost as it is way too big. Not really my code but a spaghetti code from a previous programmer. I think problems saving it to a previous version have to do with a few things:
1) Memory - I have 1 GB of RAM and I am running XP. I notice the available RAM dropping quickly as it is saving and then it blow up.
2) Long Filenames - The directory path of the original file is incorporated into the saved "previous version" of the code. While a good design, it does make the file/path a bit longer when saving
3) One of teh things it saves is the drivers and their menus. This is due to the drivers being in a subdirectory of the original code and not in the c:\program files\national instruments\labview 8.5\instr.lib directory. I saw this when I tried to save the file as an LLB.
4) If I work with smaller parts of the code without long paths, it saves fine.
There probably are xcontrols, definitely typedefs, no LVOOP's or Classes. Hope you can do something with all this. It just seems that converting to a later version of the code should be reversable. Thanks.
Michael

Passing control reference to subVI crashes labview

Hi,
using a image control (as indicator) provided by imaq Vision, I tried to pass the reference of the control to a subVI. On a computer it works and on a other (same labview version, same vision version, same os, same hardware and hardware drivers!), this crashes labview. I tried to close the control refnum at the end of the subVI, but that changed nothing to the issue. Now I use the reference as a global variable and it seems to work...nevertheless, I would like to understand what the issue and if I should remove any passing to subVI of control ref because this can potentially triggers an error. My correlated question is if this global passing is a "fake" workaround or have real chance of improving (this before going through the whole code for changing all passing of reference to subVI)
thanks a lot

Hi,
thank CoastalMaineBird for your answer
How do you know it's this issue which causes the crash?
When I remove this parameter from and the only property node in the subVi that write to it, I have no longer any problem. Moreover, to ensure that's really the "passing", and made a global variable containing the reference to this control and use my original SubVi that do access the control through its reference number
, and it works! In this last exemple, the only change is the way of transmitting the reference
What LabVIEW version?
8.0.1
up to date according Measurement & Automation update tool
Given that one computer works OK, and another crashes, I would say that
you are seeing the effect of something else, not the cause. If passing
a control ref via terminals was fatal, it would be fatal all the time.
You have some other sort of issue, perhaps timing of the different
machines triggers the bug, perhaps running out of memory, perhaps
LabVIEW is corrupted on one machine.... But I don't think changing all
your code to use globals would solve the real problem. Actually, saying that I wonder about problem of synchronisation. I know from Visual C++ that this kind of error happens if two process try to access the same control at the same time. This is typically an error changing from a computer to an other, and mutex or semaphore are the way to deal nicely with that. But does labview contains already such a securisation? If so, the global variable point on a single object and can "fell" the semaphore/mutex. But passing make a copy that will likely have two different semaphore/mutex but will point to a single control! Do someone know if I'm wrong in this idea or not?
Thanks

Auto cleanup crashes LabVIEW (and VI isn't even that large)

Hi,
I'm trying to cleanup a VI, and whenever I hit auto cleanup LabVIEW crashes and when retsrated it doesn't even say it previously crashed. I narrowed down the problem location to a for loop. The wierd thing is that I went through all the wires and objects within the loop and did auto cleanup on them but it doesn't crash. So why when I do it on all combined does it crash?
I wrote a comment in the loop that crashes to show which on it is.
I'm on Windows 7 LabVIEW 2010.0f2 32bit
I did see this posting http://digital.ni.com/public.nsf/allkb/599FB39777BDB12486257514005B7293, but even when doing it manually as suggested it still crashes.
Thanks,
Matt
Solved!
Go to Solution.
Attachments:
Score Videos temp.vi ‏126 KB

This crash corresponds to a known issue in LabVIEW (CAR #298911), which has been fixed in the forthcoming LabVIEW 2011 release. I have attached a copy of your cleaned up VI from 2011, saved for 2010. You might try to copy the block diagram into a new VI and see if that still crashes LabVIEW, but otherwise an upgrade to 2011 when it's available should clear up the problem. Hope that helps.
John B.
Embedded Networks R&D
National Instruments
Certified LabVIEW Developer
Attachments:
Score Videos temp-1.vi ‏104 KB

Internet Toolkit for G5.0 crashes Labview 8.2 during Mass Compile

I have just received my Labview 8.2 update and installed it my system along with all my toolkits. When I tried to Mass Compile Labview 8.2 directory I found that it would crash labview consistantly as shown in the attached image.
I traced this to the vi's supplied with the Internet Toolkit for G5.0.
The workaround is ...
1. Re-installed the Internet Toolkit for G5.0 into Labview 8.2
2. Mass Compiled ...\project\_config\authcfg.llb using Labview 8.0
3. Mass Compiled ...\project\_config\authcfg.llb using Labview 8.2
and there wasn't any more Labview 8.2 crashes during mass compile. As Labview 8.0 was able to mass compile the internet toolkit vi's without crashing I am suspicious that Labview 8.2 might not be completely compatible with Labview 5.0.
I posted this just in case anyone else sees a similiar issue.
David
Attachments:
Labview 8.2 Mass Compile Crash with Internet Toolkit.png ‏34 KB

David,
I was able to reproduce the crash mass compiling authcfg.llb or just trying to open the VI named 'Directory Configuration'. That code is saved in LabVIEW 5.0.1 and must have something that LabVIEW 8.2 chokes on, I'll have to get someone to investigate it. Your workaround of saving that .llb or even that one VI in 8.0 first (or probably even 7.x) is the only way I see around it with 8.2.
I do want to mention that in Q1 2004 we released version 6.0 of the Internet Toolkit and it does not exhibit this behavior. So the official solution for this crash is to upgrade to the latest Internet Toolkit.
Kennon

Simple Math VI crashes LabVIEW 2009 SP1

Hi,
We previously filed a related issue, (ref #: 7302858). The last problem was resolved by
Andy Hertzka from NI re-compiled the VI and send it back to us. That re-compilation solved the LabVIEW crashing.
However, the interesting crash happens again.
I attached a working VI before the change and a non working VI after the change and save. All the change I applied to the VI is
1. Add the "Word bits" as a connector on the diagram
2. Save it Then the VI begin to crash LabVIEW 2009 SP1.
Before the change, the VI was functioning all right.
Any idea why this might be happening? Can you try to recompile the non_working version and send it back to me for a try?
Thanks,
Tian
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB

Tian,
Like Andy I was unable to see why this code is unstable on your machine. I am able to run the code fine on my computer without any problems. Looking at the code on the block diagram I do not see any major "crash worthy" issues with it.
I have resaved the VIs like Andy had in order to fix your issue. By the way what OS are you using, windows 7? It might be helpful to save the log file for the LabVIEW crash. You should get this option when LabVIEW is restarted.
<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE>
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB

Crash LabVIEW in one click

The buggiest LabVIEW ever (8.6.1f1) keeps on giving:
WARNING: will crash LabVIEW and you will lose any unsaved work.
Open the INFO CLUSTER ctl in the attached LLB (28kB).
(Yes, I know it's ugly, I'm trying to work on it)
Right-click on the table.
Watch LabVIEW die.
Arrrgh.
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks
Attachments:
Crash-o-matic.llb ‏28 KB

Yes, I know about the overlap stuff.
Like I said, I was working on it and re-arranging stuff on the page when I discovered the bug.
Actually, I worked around it like this:
Copied the MCListBox to a blank VI.
Created a generic property node.
Linked the property node to the MCListBox.
Set the AUTOSIZE ROW height false
Set all the row heights to 23 instead of 25.
Pasted the copy in place of the original in the control I was working on.
That's what I wanted to do via dialogs, but crashed instead.
Thanks for your offer, though.
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

Bug: Windows 7 DLL call to turn off monitor message crashes LabVIEW 10.0f2

Hi,
I wanted to log this bug on the forum. I have already logged this with NI UK Support: CAR# 286873
I was trying to find a way to turn off a laptop lcd
monitor during measurements. I was trying to replicate this
http://codereflect.com/2009/04/03/how-to-programmatically-turn-onoff-your-monitor/
which uses windows messaging.
I found the attached Monitor-1.vi somewhere on the forum that seems to do the above.
However when I run the VI it crashes LabVIEW 10.f2 on Windows 7 32-bit.
cheers
David
Solved!
Go to Solution.
Attachments:
Monitor-1.vi ‏13 KB

Hi Cosmin,
That was it! Thank you so much!
I will let NI UK support that you identified the issue and get them to close the CAR.
cheers
David
Attachments:
Turn off Monitor.vi ‏12 KB

Grapher.app crashes on startup - help!

Grapher.app crashes immediately upon program start. Here's the diagnostic:
Process: Grapher [28158]
Path: /Applications/Utilities/Grapher.app/Contents/MacOS/Grapher
Identifier: com.apple.grapher
Version: 2.0 (2.0)
Build Info: GraphingCalculator-370000~1
Code Type: X86 (Native)
Parent Process: launchd [129]
Date/Time: 2008-01-28 22:09:39.427 -0600
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000000
Crashed Thread: 0
Thread 0 Crashed:
0 com.apple.AppKit 0x91e3a4a1 -[NSBezierPath appendBezierPathWithGlyphs:count:inFont:] + 39
1 com.apple.AppKit 0x91e382c3 -[NSBezierPath appendBezierPathWithGlyph:inFont:] + 56
2 com.apple.grapher 0x000775fd 0x1000 + 484861
3 com.apple.grapher 0x000785b0 0x1000 + 488880
4 com.apple.grapher 0x00077916 0x1000 + 485654
5 com.apple.grapher 0x0007446a 0x1000 + 472170
6 com.apple.grapher 0x000766bd 0x1000 + 480957
7 com.apple.grapher 0x00076799 0x1000 + 481177
8 com.apple.grapher 0x00074438 0x1000 + 472120
9 com.apple.grapher 0x0007673e 0x1000 + 481086
10 com.apple.grapher 0x000767e6 0x1000 + 481254
11 com.apple.grapher 0x00074c35 0x1000 + 474165
12 com.apple.grapher 0x00068a5a 0x1000 + 424538
13 com.apple.grapher 0x00074d47 0x1000 + 474439
14 com.apple.grapher 0x000773f2 0x1000 + 484338
15 com.apple.grapher 0x00077589 0x1000 + 484745
16 com.apple.grapher 0x000785b0 0x1000 + 488880
17 com.apple.grapher 0x00077916 0x1000 + 485654
18 com.apple.grapher 0x0007450a 0x1000 + 472330
19 com.apple.grapher 0x00074600 0x1000 + 472576
20 com.apple.grapher 0x00077aa2 0x1000 + 486050
21 com.apple.grapher 0x000745b5 0x1000 + 472501
22 com.apple.grapher 0x0007a043 0x1000 + 495683
23 com.apple.grapher 0x0006a03b 0x1000 + 430139
24 com.apple.grapher 0x0006924e 0x1000 + 426574
25 com.apple.grapher 0x0008c544 0x1000 + 570692
26 com.apple.grapher 0x0008eb7e 0x1000 + 580478
27 com.apple.grapher 0x0008c45c 0x1000 + 570460
28 com.apple.grapher 0x000d3761 0x1000 + 862049
29 com.apple.grapher 0x000d40f7 0x1000 + 864503
30 com.apple.grapher 0x000d355a 0x1000 + 861530
31 com.apple.grapher 0x000dd17a 0x1000 + 901498
32 com.apple.grapher 0x000d8fec 0x1000 + 884716
33 com.apple.grapher 0x000656a4 0x1000 + 411300
34 com.apple.CoreFoundation 0x96934a75 -[NSSet makeObjectsPerformSelector:] + 181
35 com.apple.AppKit 0x91a6056e -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1533
36 com.apple.AppKit 0x91a5679c loadNib + 264
37 com.apple.AppKit 0x91a560fd +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 946
38 com.apple.AppKit 0x91a55d40 +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 171
39 com.apple.AppKit 0x91a55c7e +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 391
40 com.apple.AppKit 0x91a5592e NSApplicationMain + 434
41 com.apple.grapher 0x0000272a 0x1000 + 5930
Thread 1:
0 libSystem.B.dylib 0x92e65ace _semwaitsignal + 10
1 libSystem.B.dylib 0x92e8fced pthreadcondwait$UNIX2003 + 73
2 libGLProgrammability.dylib 0x94582f32 glvmDoWork + 162
3 libSystem.B.dylib 0x92e8f075 pthreadstart + 321
4 libSystem.B.dylib 0x92e8ef32 thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x91e3a485 ecx: 0x909b7d58 edx: 0x00000000
edi: 0x00000000 esi: 0x00000000 ebp: 0xbfffeda8 esp: 0xbfffece0
ss: 0x0000001f efl: 0x00010246 eip: 0x91e3a4a1 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000000
Binary Images:
0x1000 - 0x147fff com.apple.grapher 2.0 (2.0) /Applications/Utilities/Grapher.app/Contents/MacOS/Grapher
0x349000 - 0x4cafef GLEngine ??? (???) <6106cebf02eec50e8f88c5dc936f1266> /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
0x542000 - 0x55efff GLRendererFloat ??? (???) <5719f596b7e2c9ef8afca208544b158b> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloa t.bundle/GLRendererFloat
0xbe70000 - 0xc176fe2 com.apple.GeForce8xxxGLDriver 1.5.18 (5.1.8) <3499aca7e7c6b2651119e4d131a888df> /System/Library/Extensions/GeForce8xxxGLDriver.bundle/Contents/MacOS/GeForce8xx xGLDriver
0xd327000 - 0xd328ff3 ATSHI.dylib ??? (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/ATSHI.dylib
0x8fe00000 - 0x8fe2d883 dyld 95.3 (???) <81592e798780564b5d46b988f7ee1a6a> /usr/lib/dyld
0x90003000 - 0x90003ff8 com.apple.ApplicationServices 34 (34) <8f910fa65f01d401ad8d04cc933cf887> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x90004000 - 0x90041ff7 libGLImage.dylib ??? (???) <202d73e6a4688fc06ff11b71910c2ce7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
0x9024b000 - 0x902fbfff edu.mit.Kerberos 6.0.11 (6.0.11) <33c25789baedcd70a7e24881775dd9ad> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x90308000 - 0x90342ff7 com.apple.coreui 0.1 (60) /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x90343000 - 0x90488ff7 com.apple.ImageIO.framework 2.0.0 (2.0.0) <154d4d8cda2bd99518cbabc9f2d69833> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
0x90489000 - 0x90493feb com.apple.audio.SoundManager 3.9.2 (3.9.2) <0f2ba6e891d3761212cf5a5e6134d683> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
0x905cf000 - 0x905dbff5 libGL.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x905dc000 - 0x905e7fe7 libCSync.A.dylib ??? (???) <df82fc093e498a9eb5490761cb292218> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x9061d000 - 0x906e4ff2 com.apple.vImage 3.0 (3.0) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
0x906e5000 - 0x906e6ffc libffi.dylib ??? (???) <a3b573eb950ca583290f7b2b4c486d09> /usr/lib/libffi.dylib
0x906e7000 - 0x9080bfe3 com.apple.audio.toolbox.AudioToolbox 1.5 (1.5) /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x9080c000 - 0x90868ff7 com.apple.htmlrendering 68 (1.1.3) <fe87a9dede38db00e6c8949942c6bd4f> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
0x90869000 - 0x90893fef libauto.dylib ??? (???) <d468bc4a8a69343f1748c293db1b57fb> /usr/lib/libauto.dylib
0x90894000 - 0x908d5fe7 libRIP.A.dylib ??? (???) <bdc6d70bf4ed3dace321b4ff76a353b3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x908d6000 - 0x90988ffb libcrypto.0.9.7.dylib ??? (???) <330b0e48e67faffc8c22dfc069ca7a47> /usr/lib/libcrypto.0.9.7.dylib
0x90989000 - 0x90a68fff libobjc.A.dylib ??? (???) <5eda47fec2d0e7853b3506aa1fd2dafa> /usr/lib/libobjc.A.dylib
0x90a77000 - 0x90aeefe3 com.apple.CFNetwork 220 (221) <972a41911805859205b057a6f5b91e8d> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x90aef000 - 0x90dc8fe7 com.apple.CoreServices.CarbonCore 783 (783) <8370e664eeb25edc98d5c1f5405b06ae> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x91032000 - 0x910b1ff5 com.apple.SearchKit 1.2.0 (1.2.0) <277b460da86bc222785159fe77e2e2ed> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x910b2000 - 0x910b3fef libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x910c9000 - 0x9113dfef libvMisc.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x9113e000 - 0x9114effc com.apple.LangAnalysis 1.6.4 (1.6.4) <cbeb17ab39f28351fe2ab5b82bf465bc> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x911b8000 - 0x911eefff com.apple.SystemConfiguration 1.9.0 (1.9.0) <7919d9588c3b0d556646e555b7193f1f> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x9135e000 - 0x91442ffb com.apple.CoreData 100 (185) <a4e63784275e25e62f57e75e0af0b94d> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x91443000 - 0x917d9ff7 com.apple.QuartzCore 1.5.1 (1.5.1) <deb61cbeb3f734a1b2f4669f6268b9de> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x917da000 - 0x917eeff3 com.apple.ImageCapture 4.0 (5.0.0) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x917ef000 - 0x91816fff libcups.2.dylib ??? (???) <5521498e8902ddd0b15cfaa7db384e29> /usr/lib/libcups.2.dylib
0x91836000 - 0x9196eff7 libicucore.A.dylib ??? (???) <afcea652ff2ec36885b2c81c57d06d4c> /usr/lib/libicucore.A.dylib
0x91a4f000 - 0x92249fef com.apple.AppKit 6.5 (949) <f8d0f6d0bb5ac092f48f42ca684bdb54> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x924b1000 - 0x92538ff7 libsqlite3.0.dylib ??? (???) <273efcb717e89c21207c851d7d33fda4> /usr/lib/libsqlite3.0.dylib
0x92539000 - 0x925cbff3 com.apple.ApplicationServices.ATS 3.0 (???) <fb5f572243dbc370a0ea5efc8e81ae11> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x92616000 - 0x9261dfe9 libgcc_s.1.dylib ??? (???) <f53c808e87d1184c0f9df63aef53ce0b> /usr/lib/libgcc_s.1.dylib
0x9261e000 - 0x92663fef com.apple.Metadata 10.5.0 (398) <4fd74fba0062c2e08ec4b1c10b40ff63> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x92664000 - 0x926beff7 com.apple.CoreText 2.0.0 (???) <7fa39cd5bc847615ec02e7c7a37c0508> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
0x926bf000 - 0x926bfffc com.apple.audio.units.AudioUnit 1.5 (1.5) /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x926c0000 - 0x929d4fe2 com.apple.QuickTime 7.4.0 (92) <0d674546d12c65dc5c33dca4c81c315b> /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
0x929fc000 - 0x92addff7 libxml2.2.dylib ??? (???) <450ec38b57fb46013847cce851001a2f> /usr/lib/libxml2.2.dylib
0x92ade000 - 0x92ae1fff com.apple.help 1.1 (36) <b507b08e484cb89033e9cf23062d77de> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
0x92ae2000 - 0x92b98fe3 com.apple.CoreServices.OSServices 210.2 (210.2) <4ed69f07fc0f211ab32d1ee96e281fc2> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x92bab000 - 0x92bc1fff com.apple.DictionaryServices 1.0.0 (1.0.0) <ad0aa0252e3323d182e17f50defe56fc> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x92ce4000 - 0x92ceafff com.apple.print.framework.Print 218 (220) <c35172175abbe554ddadd9b6401351fa> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
0x92cec000 - 0x92cecff8 com.apple.Cocoa 6.5 (???) <e064f94d969ce25cb7de3cfb980c3249> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x92ced000 - 0x92d1cfe3 com.apple.AE 402 (402) <994ba8e884aefe7bf1fc5987df099e7b> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x92d1d000 - 0x92d2afe7 com.apple.opengl 1.5.5 (1.5.5) <aa08b52d2a84b44dc6ee5d544a53fe8a> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x92d2b000 - 0x92d84fff libGLU.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x92d85000 - 0x92d85fff com.apple.Carbon 136 (136) <98a5e3bc0c4fa44bbb09713bb88707fe> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x92df6000 - 0x92e1afff libxslt.1.dylib ??? (???) <4933ddc7f6618743197aadc85b33b5ab> /usr/lib/libxslt.1.dylib
0x92e1b000 - 0x92e5dfef com.apple.NavigationServices 3.5.1 (161) <cc6bd78eabf1e2e7166914e9f12f5850> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
0x92e5e000 - 0x92fb8fe3 libSystem.B.dylib ??? (???) <8ecc83dc0399be3946f7a46e88cf4bbb> /usr/lib/libSystem.B.dylib
0x92fcd000 - 0x9302affb libstdc++.6.dylib ??? (???) <04b812dcec670daa8b7d2852ab14be60> /usr/lib/libstdc++.6.dylib
0x93fc0000 - 0x93fceffd libz.1.dylib ??? (???) <5ddd8539ae2ebfd8e7cc1c57525385c7> /usr/lib/libz.1.dylib
0x93fd9000 - 0x94018fef libTIFF.dylib ??? (???) <6d0f80e9d4d81f3f64c876aca005bd53> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x94049000 - 0x940f8fff com.apple.DesktopServices 1.4.3 (1.4.3) <66d5ed56111c43d234e235d365d02469> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x940f9000 - 0x941c4fff com.apple.ColorSync 4.5.0 (4.5.0) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
0x941ca000 - 0x941cffff com.apple.CommonPanels 1.2.4 (85) <ea0665f57cd267609466ed8b2b20e893> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x941d0000 - 0x941fdfeb libvDSP.dylib ??? (???) <a26683d121ee0f96df9a9d0bfca36049> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x941fe000 - 0x9424eff7 com.apple.HIServices 1.6.0 (???) <d74aa73e4cfd30a08fb169198a8d2539> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x9424f000 - 0x942c9ff8 com.apple.print.framework.PrintCore 5.5 (245) <9441d178f4b430cf92b67bf346646693> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
0x942ca000 - 0x942d3fff com.apple.speech.recognition.framework 3.7.24 (3.7.24) <d3180f9edbd9a5e6f283d6156aa3c602> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x942d4000 - 0x942ecfff com.apple.openscripting 1.2.6 (???) <b8e553df643f2aec68fa968b3b459b2b> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x942ed000 - 0x9430bfff libresolv.9.dylib ??? (???) <54e6a08c2f108bdf5916fb483d51961b> /usr/lib/libresolv.9.dylib
0x9430c000 - 0x94398ff7 com.apple.LaunchServices 286 (286) <72b15e7a01e42d510f0339e90113d5d6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x94461000 - 0x944ebfff com.apple.framework.IOKit 1.5.1 (???) <5176a7383151a19c962334009fef2c6d> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x9455c000 - 0x94a28ffe libGLProgrammability.dylib ??? (???) <e8bc0af671427cf2b6279a035805a086> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgramma bility.dylib
0x94a29000 - 0x94de7fea libLAPACK.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x94de8000 - 0x94e64feb com.apple.audio.CoreAudio 3.1.0 (3.1) <70bb7c657061631491029a61babe0b26> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x94e65000 - 0x9502efef com.apple.security 5.0.1 (32736) <8c9eda0fcc1d8a571543025ac900715f> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x9503b000 - 0x9503bffd com.apple.Accelerate 1.4 (Accelerate 1.4) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x95081000 - 0x95081ffa com.apple.CoreServices 32 (32) <2fcc8f3bd5bbfc000b476cad8e6a3dd2> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x951a9000 - 0x951d3fff com.apple.CoreMediaPrivate 1.4 (1.4) <59630ee9096ecf2ca1e518da2f46c68d> /System/Library/PrivateFrameworks/CoreMediaPrivate.framework/Versions/A/CoreMed iaPrivate
0x951e4000 - 0x951f4fff com.apple.speech.synthesis.framework 3.6.59 (3.6.59) <4ffef145fad3d4d787e0c33eab26b336> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x951f5000 - 0x9520bfe7 com.apple.CoreVideo 1.5.0 (1.5.0) <7e010557527a0e6d49147c297d16850a> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x9520c000 - 0x95485fe7 com.apple.Foundation 6.5.1 (677.1) <85ac18c7cd454378db6122bea0c00965> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x954fb000 - 0x954fffff libGIF.dylib ??? (???) <d4234e6f5e5f530bdafb969157f1f17b> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x95500000 - 0x95500ffd com.apple.Accelerate.vecLib 3.4 (vecLib 3.4) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
0x95501000 - 0x9553efff com.apple.CoreMediaIOServicesPrivate 1.4 (1.4) /System/Library/PrivateFrameworks/CoreMediaIOServicesPrivate.framework/Versions /A/CoreMediaIOServicesPrivate
0x955de000 - 0x955e5ffe libbsm.dylib ??? (???) <d25c63378a5029648ffd4b4669be31bf> /usr/lib/libbsm.dylib
0x955e6000 - 0x955e8ff5 libRadiance.dylib ??? (???) <20eadb285da83df96c795c2c5fa20590> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x95636000 - 0x95636ffd com.apple.vecLib 3.4 (vecLib 3.4) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x95637000 - 0x956c3ffb com.apple.QTKit 7.4 (92) /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
0x956c4000 - 0x959cafff com.apple.HIToolbox 1.5.0 (???) <1b872a7151ee3f80c9c736a3e46d00d9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x959cb000 - 0x959d3fff com.apple.DiskArbitration 2.2 (2.2) <1551b2af557fdf6f368f93e093933852> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x95b91000 - 0x95fa1fef libBLAS.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x95fa2000 - 0x96035fff com.apple.ink.framework 101.3 (86) <bf3fa8927b4b8baae92381a976fd2079> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x96087000 - 0x96087ffb com.apple.installserver.framework 1.0 (8) /System/Library/PrivateFrameworks/InstallServer.framework/Versions/A/InstallSer ver
0x96088000 - 0x960a7ffa libJPEG.dylib ??? (???) <0cfb80109d624beb9ceb3c43b6c5ec10> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x960a8000 - 0x9673ffef com.apple.CoreGraphics 1.351.0 (???) <7a6f399039eed6dbe845c169f7d21a70> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x96740000 - 0x967e7fff com.apple.QD 3.11.50 (???) <e2f71720ae1dad06a8883ac80775b21a> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
0x9681b000 - 0x96836ffb libPng.dylib ??? (???) <b6abcac36ec7654ff3e1cfa786b0117b> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
0x96837000 - 0x96839fff com.apple.securityhi 3.0 (30817) <2b2854123fed609d1820d2779e2e0963> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
0x9683a000 - 0x9696cfe7 com.apple.CoreFoundation 6.5 (476) <8bfebc0dbad6fc33bea0fa00a1b9ec37> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0xba900000 - 0xba916fff libJapaneseConverter.dylib ??? (???) <7b0248c392848338f5d6ed093313eeef> /System/Library/CoreServices/Encodings/libJapaneseConverter.dylib
0xfffe8000 - 0xfffebfff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
The point of crash seems suspicious... am I missing a font that Grapher needs?

It turned out it was a font problem. I had installed Linotype's FontManager (bad idea--it moved all my fonts out of their default directories), and uninstalled it, but it left some junk in my user Preferences folder. Deleting that junk fixed the problem.

Crash LabVIEW

In the zip file are two vi's. The "Crash LabVIEW.vi" vi uses a subpanel to open the other vi "just a while loop.vi". When the stop button is pressed on "Crash LabVIEW.vi", it sends the data to the stop button on the "just a while loop.vi". It works fine, but read the comments in the "Crash LabVIEW.vi". It was a simple mistake, but still no error message, nothing, just LabVIEW disappearing off the screen and off the task manager... I guess you can't compare apples and oranges, even though LabVIEW will let you try.
Attachments:
Crash LabVIEW.zip ‏21 KB

Hi Dominick,
I was able to reproduce this crash. You are right in that LabVIEW shouldn't crash without an error. This was reported to R&D (# 101959) for further investigation. Thanks for the feedback.
Regards,
Stanley Hu
National Instruments
Applications Engineering
http://www.ni.com/support

GetDefaultPrinters (WinAPI call) Crashes Labview

Hi all,
For several reasons I need to use the windows API to get the default printer. I know about labview's activex solutions but those are not universal.
See attached VI. This winapi call crashes labview rather consistently. It runs fine and returns correctly the default printer. However, some time later, a few seconds or a few operations later it will always crash labview. Why? I've tried changing it to "Run in UI thread" instead of any thread but neither seems to help...
To get it to crash immediately, try closing the VI. That seems to do it every time. Access violations...
Solved!
Go to Solution.
Attachments:
defaultprinters.vi ‏10 KB

No. You actually did NOT allocated memory in your VI.
Here is how to allocated memory, the old way:
George Zou
http://webspace.webring.com/people/og/gtoolbox

Graph Curser doesn't update

I have a X-Y Graph the has a plot of Temperature vs Time.
The graph has
curser that is locked to the plot. As I move the curser through
different points the curser X and Y positions update. However if I move
the curser over a point which has NaN Temperature the curser's Y
position does not update. The Xposition (time) updates but the
Temperature shows the old value instead of the NaN. As you can
see in the picture the curser is over a point which is NaN but read out
shows 218.85. The funny thing is that if you minimize and maximize the
screen it will update the read out! I think this is one of the other
bugs that needs to be fixed in the next LabVIEW. Any inputs or
suggestion as to how to get around this bug in LabVIEW is greatly
appriciated.
Message Edited by Nariman on 07-05-2005 12:00 PM
Attachments:
picture1.jpg ‏49 KB

I can confirm this in 7.0. An example is attached.
Note that this only happens if you move the cursor sideways. If you grab the cursor where the point is (it's shaped like a cross), it will snap to the closest point (so that's your workaround).
To submit a bug, use the email option here. Include a link to this page.
Try to take over the world!
Attachments:
Plot bug.vi ‏28 KB

Spectrogram Graph Curser Crashes Labview

Similar Messages

Maybe you are looking for