hello. i'm new to forums and hope i don't leave out too much about the problem. but from what i've read through, i'll post what i hope is helpful to get a basic intro on the situation.
i'm using labview 8.6 on a macbook pro (i can give out specs if necessary). i've been working on a VI that simulates low count fluorescence lifetime imaging to aide a previous professor of mine in my masters thesis work. i've since graduated, but am still looking to continue this work because i feel it would be helpful to the university and gives me more practice with various programming methods, currently monte carlo simulations.
that being said, i had a working simulation running not long ago. i use the call library function node to input C libraries which i create in Xcode. i have and use the CIN 8.5 plugin to ensure labview reads the file correctly. and that has been the case for a while. i modify the files, add the new parameters, select the function name, and run the program.
then recently everything stopped working. and for the life of me, i cannot seem to figure out why. i added a new library function node to the VI (bringing the total count to 4), added the parameters, and it crashed when i ran it. there was nothing done differently between that library function call and any other, so it confuses me. the one thing that stood out was that the function name, which usually comes up in the drop list, didn't show up and i had to manually add it. the code was set up identically to the others already working in the VI, so i tried to debug it for memory allocation faults or uninitiated arrays. i found nothing, so i modified it to do nothing complex, just output one number. it still didn't work. thinking maybe it is just that particular library function, i took the code and inserted it into one of the existing library function nodes, compiled it, and tried to run the program. once again, it crashed. i've noticed that now all of my library nodes, in the .bundle format, cannot find their associated function names when i specify their paths. the only thing i can think that i did between when the library nodes worked and stopped working was start to mess around with trying to write an iPhone application using the simulator and some practice files to see how everything worked. i don't see how that could affect it, but it's worth pointing out. i should probably note that when i compile and build my libraries, i use Mac OS X 10.6 as the active SDK, Devopment as the active configuration, and i386 as the active architecture. this is the same setup i've used for all codes.
i hope this is enough to at least get started on some sort of solution. if anything else needs to be known, please ask and i'll clear up what i can. i've attached the crash report that i get when i try to run the program in case that helps at all.
thank you,
justin
