Labview merge crashes
We've just moved from 8.2 to 8.5, including a recompile of all our .vi's.
LVMerge seemed like an exciting new feature - unfortunately, it crashes on us on all but the most trivial .vis. Only a few, specially-created (tiny, very simple) vi's do not result in a crash for us. The crash is usually not accompanied by an error message, but occasionally a message about fpsane.cpp (line 367) comes up - this is probably a separate problem, related to an (already-noted) issue in the knowledge base about locking tabs (although I'm not sure why opening in lvmerge would result in locking a tab).
We've tried a lot of different conditions - running straight from the GUI, the command line, subversion's context menu (identical to running from the command line). We've tried copy/pasting just the controls into a new .vi (for all three of the merging .vis), ommitting the code. Nothing seems to help.
We're running Windows XP, LV 8.5, using subversion for source control.
Anyone else having this issue? Any workarounds?
Regards,
Don
Hi Don,
I would suggest going to www.ni.com/ask and creating an email service request. You are welcome to post the files that are causing you problems to the forum, but an individual service request is probably the best avenue to resolve this issue.
Brian R.
District Sales Manager
Washington DC
National Instruments
Similar Messages
-
LabVIEW 2009 crashes at startup with the presence of a certain CRT version on the system
When installing our LabVIEW integration package on a system running
LabVIEW 2009 LabVIEW will crash at startup afterwards. Using 'dependency
walker' reveals, that 'nicont.dll' causes this crash because of a
side-by-side configuration problem. After some debugging I found out
that on this particular system installing a certain version of the
Microsoft CRT will stop LabVIEW from functioning. My fix now is to
recompile our code with a newer version of VS. I now ship a VS9 version
of the runtime and everything is working as expected.
However
I guess the real problem lies within the LabVIEW installer. I guess a
needed version of the CRT is not installed by LabVIEW. It still works
because due to some policy files on the machine it gots defaulted to a
compatible version at startup. However when I install the following 2
merge modules on the target system LabVIEW does no longer work:
Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.762)
policy_8_0_Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.4053)
Renaming
the *.policy file in the SxS dir on the target system gets LabVIEW back
to run, but of course other SW needing this file does not run then
I was using XP, 32 bit SP 3
I can provide additional information if needed. Is this a known problem? Is there a fixed version of LabVIEW already?
Message Edited by anotherStefan on 02-05-2010 05:44 AMSure! I tried to attach the installer causing the problem to this message.
However I failed miserably(BAD GATEWAY from the upstream server). Where can I upload the installer to or what do I need to do?
It will install some other stuff as well (A bunch of VIs, a DLL and an
OCX(this needs the CRT I have trouble with)and the CRT and MFC runtimes I
mentioned. An updated version of the installer can be obtain here(however it does no longer show the issue):
http://www.matrix-vision.com/functions/count.php?url=products/hardware/family/SC/mvBlueFOX/LabVIEW_a...
The only difference between the two packages is, that the OCX in the
attached file has been build using VS2005SP1 and in the package the link
points to I did use VS2008. Apart from that I changed the 2 merge
modules from Microsoft (CRT and MFC) -
LabVIEW is crashing when i am trying to build the exe
I am trying to build an executable from a program in which i am communicating with several instruments, whenever i am trying to build an exe labview is crashing and i am getting the error Exception: access violation(0xc0000005)at eip=0x10054DD1.
after reading some posts on forum i tried builduing an exe on other system also, but still i am getting the same error.
below i am attaching the program and the image of the error i am getting.
Attachments:
labview crash.png 53 KB
automation.zip 4455 KBRitu wrote:
waiting for the reply....
Realize this community is by a large majority volunteer based. If you need urgent support contact NI directly
http://sine.ni.com/apps/utf8/nicc.call_me?loc=en-US
That being said I would try to disable the large amount of code. Say you have a Main that launches a bunch of stuff, put a disabled diagram code around the launching part and then try to rebuild. It is a very slow process (especially when the build takes a while to fail) but by doing this you can more isolate the parts of the code that can cause the crash. The only time I've seen a crash on build like you described, I simply rebooted and it was fine. Usually because of my own fault by stopping code in a bad way previously leaving things in memory.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously. -
Running the VI causes LabVIEW to crash
Hello
While debugging a SW, I found that a particular VI, when run, causes LabVIEW to crash. This happens whether this VI is called while executing an exe or called by higher VI or even when it is run separately.
The VI to be run is NLD_Test_PP_Plot.vi present in the folder "Generic VI's".
The input for this VI is .csv file, which is attached. The csv file needs to be placed in a separate location and that path needs to be entered in the string constant in the VI.
Note: This VI is developed and run in LV v2009.
Thanks
Sharath
Attachments:
SpecimenCW_20150407_193059.csv 67 KB
NLD_Test_PP_Plot Folder.zip 208 KBLabVIEW did not crash for me (nor did it throw an error). It made a bmp of your data and then exited. I am using LV 2013.
Did it actually crash or did it throw an error? If it crashed, do you have the crash zip file?
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all. -
Deny Access function with invalid file refnum causes LabVIEW to crash
Hi folks,
I have LabVIEW 8.5, and today encountered something interesting that consistently causes LabVIEW to crash. Essentially, if you find the "Deny Access" function under the advanced file IO palette and wire up an invalid refnum, Windows (XP in my case) reports that LabVIEW has to close. I checked in task manager, and the LabVIEW process is still active and using a disproportionate amount of the CPU.
To reproduce the issue, simply drop the function on your block diagram, create a constant from the refnum input terminal, and run the VI. Has anyone else seen this behavior?
Thanks,
JimHi Carla,
I'm glad to help, and thanks for looking into it. The way I ran into the bug was while I was working on an action engine VI to log certain text values (see attached picture). While logging, I didn't want other programs to access the file. When a new file had to be generated, I wanted to stop denying access and close the reference. However, if the value on the shift register was invalid, LabVIEW crashed instead of throwing an error (I guess a crash qualifies as an error).
If you look at the attached picture, my workaround was to use the "Not A Number/Path/Refnum?" function. If the reference is bad, I don't try to use the "Deny Access" funtion or close the file. That worked just fine and seems like a good solution for now.
Jim
Attachments:
Logger.png 6 KB -
Labview 2013 crashing when restarting VI
My VI runs and I have no problems.
If I stop then Vi and re-run it, pretty much every second time it crashes. It does not point to anything and the only message I get is:
Problem signature:
Problem Event Name: APPCRASH
Application Name: LabVIEW.exe
Application Version: 13.0.0.4051
Application Timestamp: 525595c6
Fault Module Name: NiViPxi.dll
Fault Module Version: 5.4.0.49152
Fault Module Timestamp: 51c243ad
Exception Code: c0000005
Exception Offset: 0000bbe0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 6153
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
This only clue in the above I can find is NiViPxi.dll
I am using a PXI rack so maybe it is to do with one of the devices?
I would be nice to have more clues, does anyone know why labVIEW keeps crashing?
Rgds,
Sean
Solved!
Go to Solution.Hi jinfone.t
I managed to root cause it to a netway 72 PXI dll and have fixed the issue, (took a lot of effort!)
- Does the crash only occur when you re run this particular VI that you are talking about?
Yes
- Is there any crash logs generated?
None that I know of apart from the output I pasted on the screen. It's possible there is something in the event monitor
- What does your VI do?
It function tests our product, (IOT)
- Would it be possible to show the code?
I'm afraid not as it is proprietary. However, the issue appears to be due to the dll. Netway may release the VIs but I believe you are required to buy hardware/ software.
The issue I have is that LabVIEW is not handling this crash well at all. It does not point to the problem dll nor does it drop a fail log that I know of.
Thanks for the feedback.
Ciao,
Sean -
Labview 8 crashes when saving a vi with a 'Bundle By Name' function
We have a working vi (Get_AN_Fast.vi), created with Labview 7.1.
Trying to open this vi with Labview 8 crashes Labview.
Problem seems to be related to a 'Bundle by Name' function, but it is not that simple as using this function by itself wirks fine.
Any ideas would be a help.
Attachments:
Labview_Upgrade_Crash.zip 117 KBSorry for the delay, I have been testing on other machines.
We can reproduce the error on other machines, with completly fresh installs of Labview 8.
The ActiveX Object we are connecting to is our own COM server, for interfacing to USB based data acquisition devices.
I have found that when our COM server is not installed on a computer, then the VI will open, but with errors related the the missing COM Server.
When the COM Server is installed, Labview 8 crashes when opening the vi.
I realise that our COM server might have bugs, but it worked fine with Labview 6 and 7, and it is Labview 8 that gives the error, not our COM Server (which is a stand-alone executable).
I have attached a zip file with our COM server, it just needs to be unzipped to a temporary file, and then run the 'register.bat' file to register the server.
It will not install any other files on your computer and, can just be deleted when you are finished.
Thanks
Charlie.
Attachments:
COM_Server.zip 659 KB
Labview_Upgrade_Crash.zip 117 KB -
Is there any use for using LabVIEW merge if your software team does not to parallel development? We are starting to setup Perforce for source control, and I was considering setting up LVMerge.exe to work with Perforce. However, since we have no parallel development, I don't see any point to this. Is there a reason that I'm overlooking to setup and use LVMerge when there is no parallel development?
Thanks!Dennis Knutson wrote:
Consider a single developer making multiple changes. Merge is just not for different users. I've had to do a quick patch to fix a bug in source while at the same time, do more extended edits on the same source for new release with additional features.
Now that I think about it, I was confused how a single user would use LVMerge, because I don't really understand some of the differences between the arguments LVMerge uses. What is the difference between the Base VI and Your VI? According to the LabVIEW help, the Base VI is "Absolute path to a copy of the VI from where you checked it out (Base
VI)," and Your VI is "Absolute path to the VI you edited (Your VI)." Those seem like the same things to me. Isn't the VI I checked out the one that I am editing? Could someone clear that one up for me?
Also, I am confused about Their VI, which according to the LabVIEW help is, "Absolute path to a copy of the latest revision of the VI in source control
(Their VI)." MY source control is on a server. Do I use the server absolute path, like \\SERVER\SourceControl\Project\VI.vi to tell LVMerge where to get that VI? -
Labview 2014 crashing(windows 7)
Hello for some reason my labview 2014 crashes when i try to open the labview application. It was working fine until yesterday but not having any luck today. Also i cannot see my labview software in the programs and feature section on the control panel even though i have administrative privileges in my computer. I have attached my error report below.Any help would be appreciated.
Attachments:
crash_report.PNG 109 KBHi go_sa,
In Programs and Features are you looking under National Instruments Software for LabVIEW 2014? If so, and LabVIEW is not listed, have you tried re-installing the software?
If it is listed under National Instruments Software, it sounds like there may be some software corruption causing the error. The next step would be to try repairing the program. If this does not work, you can try force re-install the program (link below) or uninstalling and reinstalling it.
http://digital.ni.com/public.nsf/allkb/ADD22E807D5A12AD862579EC00760F79
Julia P. -
Hi there,
I have just run into some very strange behaviour in LabVIEW (7.0 on Win2k with service pack 2).
I have an event structure with several user events (about 12) listed in it. Everything was working fine yesterday. Today I tried to add another user event to the structure and LabVIEW crashed (giving usual cryptic error message saying referenced memory could not be read).
Now, I have experimented quite a bit, and have the following observations to give:
LabVIEW is happy adding more events until I try and add an event if the currently selected event is a Filter event (i.e Mouse Down?).
I have a certain Mouse Down? filter event, and if I change this to a non-filtered Mouse Down event then LabVIEW lets me add more event cases as normal. However, I need this to be a filtered event (i.e with the "?"), and in this case, the next I try and add results in the LabVIEW IDE crashing. I can add more events as long as I dont have a filtered event case currently selected, so I suppose this is a work-around.
To clarify, this occurs when I am trying to add events at design time, not at run time.
I tried to replicate this in a new VI, and everything works fine as expected :-(
I can't really attach the VI.
Has anybody else noticed behaviour like this???
nrp
CLAhi there
thanks for your suggestions
>> A couple of suggestions:
>>1. Try opening the VI on a different computer\LV version.
>>2. Try copying all the code in the VI into another VI and see if this still happens.
>>3. Start deleting pieces of the VI until it stops (or there is nothing left).
I tried options 2 (same crash) and option 3 (crash stops when I delete the Filter events) before I posted the question.
I have tried opening the VI on another PC (also Win2k) with the same version of LabVIEW and it also crashes.
sigh...
I suppose I am just going to have to work around it for now... strange bug...
nrp
CLA -
Using New LabVIEW Merge Tool LVMerge With Tortoise SVN
Hi,
I've just posted a new blog article Using New LabVIEW Merge Tool LVMerge With Tortoise SVN to my blog at ExpressionFlow. Check it out!
Tomi
Tomi MailaThe LV merge tool really does become far more powerful when integrated into SVN than when used manually. Here's an article on Using LVmerge LabVIEW Merge Tool with TortoiseSVN with all the necessary setup instructions for LabView 8.5 and 8.6.
Jesse -
Bind FPGA host reference to type definition in labVIEW 2012 crashes labVIEW
Hi,
I am using FPGA target device 5641R and labview FPGA 2012 with 5640R ver 1.7.
On the configure window of open FPGA VI reference function, choosing the dynmaic mode shows broken arrow when wired to the 5640R configuration VIs (i.e. Configure timebase, Configure ADC default, Configure ADC NCO functions). So i tried the other option which is binding the FPGA host reference to type definition and choose the control from path C:\Program Files\National Instruments\LabVIEW 2012\instr.lib\ni5640R\Configuration\NI-5640R VIs\ni5640R FPGA VI Reference.ctl. But after that when i try to save the VI on which open FPGA VI reference function is placed, labVIEW crashes. I am unable to figure out the reason. Earlier I was working with labVIEW 2011 and it was working fine there. Any suggestions would be highly appretiated.
Please see the attached images for more details.
Thanks
Attachments:
1.png 33 KB
2.png 71 KB
3.png 40 KBCheck out this thread. It looks like someone else ran into a similar issue and made changes that fixed their application.
http://forums.ni.com/t5/IF-RIO/correct-5640r-template-use-recommendation/td-p/1331918
Jeff B.
Applications Engineer
National Instruments -
"Using a CIN to Create an Array of Strings in LabVIEW" example crashes LV on Linux
Tried to utilize this NI example: "Using a CIN to Create an Array of Strings in LabVIEW" (http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B4B282BE7EF907C8E034080020E74861&p_node=&p_source=External)
Compiles OK with the makefile made by the LV's lvmkmf utility. Nevertheless when I try to run the VI (with the code loaded into the CIN, of course), LabVIEW 7.1.1 on a SUSE 9.3 Linux machine crashes:
LabVIEW caught fatal signal
7.1.1 - Received SIGSEGV
Reason: address not mapped to object
Attempt to reference address: 0x0
Segmentation fault
Any ideas? Did anybody try this on a Windows machine?H View Labs wrote:
Tried to utilize this NI example: "Using a CIN to Create an Array of Strings in LabVIEW" (http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B4B282BE7EF907C8E034080020E74861&p_node=&p_source=External)
Compiles OK with the makefile made by the LV's lvmkmf utility. Nevertheless when I try to run the VI (with the code loaded into the CIN, of course), LabVIEW 7.1.1 on a SUSE 9.3 Linux machine crashes:
LabVIEW caught fatal signal
7.1.1 - Received SIGSEGV
Reason: address not mapped to object
Attempt to reference address: 0x0
Segmentation fault
Any ideas? Did anybody try this on a Windows machine?
This code is badly broken. In addition to resizing the actual handle to hold the number of string handles you also would need to create the string handles itself before attempting to write into them. NumericArrayResize is the fucntion to use as it will either resize an existing handle (if any) or create a new one if the value is uninitialized (NULL).
/* resize strarr to hold handles to NUMSTRINGS strings */
err = SetCINArraySize((UHandle)strarr, 0, NUMSTRINGS);
if (err)
goto out;
/* perform this loop once for each element */
/* of array of strings being created */
for (i = 0; i < NUMSTRINGS;) {
LStrHandle handle = (*strarr)->arg1[i];
/* determine length of string that will be element of strarr */
strsize = StrLen(str[i]);
err = NumericArrayResize(uB, 1, &handle, strsize);
if (err)
goto out;
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
/* moves strsize bytes from the address pointed to */
/* by str[i] to the address pointed to by the data pointer in the handle */
MoveBlock(str[i], LStrBuf(*handle), strsize);
/* manually set size of string pointed to by *strarr */
(*((*strarr)->arg1[i]))->cnt = strsize;
/* manually set dimSize of strarr */
(*strarr)->dimSize = ++i;
return noErr;
out:
return err;
Rolf KalbermatterMessage Edited by rolfk on 06-30-2005 03:15 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions -
Labview 8 crashes when using Read Labview Measurement File
Hi All,
I am a new user for Labview. I installed Labview 8.0 from the CD (evaluation copy). I was just testing the sample code provided by NI. I opened the "Load from File and Display" example and I was trying to open the properties for the Read Labview Measurement File component when Labview crashed. I tried it a couple of times and everytime it happens the same way (when I double click the component or right click on it).
I am using Windows XP with all the updates done. In the Windows crash report, the application version is 8.0.0.4005.
Other problem I encountered is a missing component on the Input Palette (no DAQ Assistant present) and the Instrument I/O Assistant raises the error "Measurement & Automation Explorer or the Instrument I/O Assistant is not installed correctly. Please install these from the Labview Driver CD". For the last problem, I will try to run the Labview Driver CD, once I get it. But I am not sure if the DAQ Assistant will show up then or not.
Any ideas?
Regards,
NickHello Nick,
While it is not my area of expertise, I would expect the DAQ Assistant would appear after installing the driver CD as you said you would be trying.
What caught my attention was the crash. The easiest way to resolve the crash is to delete the instance of the Read LabVIEW Measurement File on the diagram and place a new one from the Express Input palette (now called "Read From Measurement File"). In that situation, I would expect just pressing OK to accept the default configuration should work. The crash occurs in certain circumstances when the Read / Write Measurement File Express VIs are dropped from a previous version of LabVIEW and then their config page is opened in 8.0.x. This issue should be resolved in a future release, sorry for the inconvenience. -
This has probably been answered. Please link me to the solution if its been addressed already.
Data Merge Indesign CS2 crashes once I click "Create Merge Document"
Process: Adobe InDesign CS2 [94022]
Path: /Applications/Adobe InDesign CS2/Adobe InDesign CS2.app/Contents/MacOS/Adobe InDesign CS2
Identifier: com.adobe.InDesign
Version: 4.0.5.688 (4050)
Code Type: PPC (Translated)
Parent Process: launchd [98]
Date/Time: 2011-02-11 15:05:16.508 -0600
OS Version: Mac OS X 10.6.6 (10J567)
Report Version: 6
Interval Since Last Report: 1304888 sec
Crashes Since Last Report: 458
Per-App Interval Since Last Report: 5785 sec
Per-App Crashes Since Last Report: 6
Anonymous UUID: 7A37D15A-1CF1-4B3C-9B73-C53FFD992474
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0
Thread 0 Crashed:
0 com.adobe.InDesign 0xb80c5d10 0xb8000000 + 810256
1 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
2 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
3 com.adobe.InDesign 0xb8145c1d spin_lock_wrapper + 3973
4 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 1:
0 libSystem.B.dylib 0x801430fa mach_msg_trap + 10
1 libSystem.B.dylib 0x80143867 mach_msg + 68
2 com.adobe.InDesign 0xb819440f CallPPCFunctionAtAddressInt + 206231
3 libSystem.B.dylib 0x8017085d _pthread_start + 345
4 libSystem.B.dylib 0x801706e2 thread_start + 34
Thread 2:
0 com.adobe.InDesign 0xb815acc0 spin_lock_wrapper + 90152
1 com.adobe.InDesign 0xb8179c5b CallPPCFunctionAtAddressInt + 97763
2 com.adobe.InDesign 0xb80e88cb 0xb8000000 + 952523
3 ??? 0xcb6abe4a 0 + 3412770378
Thread 3:
0 com.adobe.InDesign 0xb815aa8b spin_lock_wrapper + 89587
1 com.adobe.InDesign 0xb818c3eb CallPPCFunctionAtAddressInt + 173427
2 com.adobe.InDesign 0xb818eeec CallPPCFunctionAtAddressInt + 184436
3 com.adobe.InDesign 0xb80e88cb 0xb8000000 + 952523
4 ??? 0x8aace216 0 + 2326585878
Thread 4:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145397 spin_lock_wrapper + 1791
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 5:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145397 spin_lock_wrapper + 1791
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 6:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145397 spin_lock_wrapper + 1791
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 7:
0 com.adobe.InDesign 0xb815a8c8 spin_lock_wrapper + 89136
1 com.adobe.InDesign 0xb8176d61 CallPPCFunctionAtAddressInt + 85737
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145c1d spin_lock_wrapper + 3973
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 8:
0 com.adobe.InDesign 0xb815aa8b spin_lock_wrapper + 89587
1 com.adobe.InDesign 0xb818c3eb CallPPCFunctionAtAddressInt + 173427
2 com.adobe.InDesign 0xb818eeec CallPPCFunctionAtAddressInt + 184436
3 com.adobe.InDesign 0xb80e88cb 0xb8000000 + 952523
4 ??? 0x8aace216 0 + 2326585878
Thread 9:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80e88cb 0xb8000000 + 952523
3 ??? 0x8bac77ea 0 + 2343335914
Thread 10:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80e88cb 0xb8000000 + 952523
3 ??? 0x8bac77ea 0 + 2343335914
Thread 11: com.apple.CFSocket.private
0 com.adobe.InDesign 0xb815ac81 spin_lock_wrapper + 90089
1 com.adobe.InDesign 0xb816ad6f CallPPCFunctionAtAddressInt + 36599
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145c1d spin_lock_wrapper + 3973
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
7 ??? 0xf0592a90 0 + 4032375440
Thread 12:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80e88cb 0xb8000000 + 952523
3 ??? 0x8bac77ea 0 + 2343335914
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0xb80c5ce8 ecx: 0x00000000 edx: 0x00000002
edi: 0x00000000 esi: 0x80a059a0 ebp: 0xb7fffa08 esp: 0xb7fff9d0
ss: 0x0000001f efl: 0x00010202 eip: 0xb80c5d10 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000000
Binary Images:
0x3fffa000 - 0x3fffbff7 BDL.dylib 38.0.0 (compatibility 1.0.0) <7962366F-BF58-160E-0B73-338F0736B27C> /usr/libexec/oah/Shims/BDL.dylib
0x3ffff000 - 0x3ffffff7 libSystem.B.dylib 38.0.0 (compatibility 1.0.0) <63852FDA-04FA-AAA0-67E6-CBB15F6920F1> /usr/libexec/oah/Shims/libSystem.B.dylib
0x40003000 - 0x40005ff7 CoreFoundation 38.0.0 (compatibility 150.0.0) <F267D656-C1AD-07A8-2CCC-9D40323BE626> /usr/libexec/oah/Shims/CoreFoundation.framework/CoreFoundation
0x40013000 - 0x40013ff7 ApplicationServices 38.0.0 (compatibility 1.0.0) <3CCC383E-7267-5DBD-BFFF-DF0132FED485> /usr/libexec/oah/Shims/ApplicationServices.framework/ApplicationServices
0x40017000 - 0x4001bff7 libGFXShared.dylib ??? (???) <9E14BE2F-C863-40E9-41A6-1BE9045663A0> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
0x403e1000 - 0x403e4ff7 libCoreVMClient.dylib ??? (???) <973B9E1F-70B3-2E76-B14B-E57F306AD2DF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
0x407a0000 - 0x407a8ff7 IOKit 38.0.0 (compatibility 1.0.0) <DCA9B384-0F69-C525-ED46-383C34F025ED> /usr/libexec/oah/Shims/IOKit.framework/IOKit
0x407ae000 - 0x407b2ff7 IOSurface ??? (???) <235E7E3D-B6E5-0AAA-C41A-7AC1F54A7EBF> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
0x40ef8000 - 0x40f2dff7 GLEngine ??? (???) <68F67685-19B4-CB0E-6CE2-89A0F87BEAEE> /usr/libexec/oah/Shims/GLEngine.bundle/GLEngine
0x415cf000 - 0x41600ff7 libGLImage.dylib ??? (???) <E3EC8E92-4DDD-E7B8-3D38-C5A5160A4930> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x4165c000 - 0x41680fe7 GLRendererFloat ??? (???) <1274B762-2FB9-48FE-EAFD-C459B2B4BECC> /System/Library/Frameworks/OpenGL.framework/Resources/GLRendererFloat.bundle/GLRendererFl oat
0x80000000 - 0x8005dff7 com.apple.framework.IOKit 2.0 (???) <A769737F-E0D6-FB06-29B4-915CF4F43420> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x8007d000 - 0x800e7fe7 libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib
0x80142000 - 0x802e9ff7 libSystem.B.dylib 125.2.1 (compatibility 1.0.0) <4FFBF71A-D603-3C64-2BC6-BFBFFFD562F0> /usr/lib/libSystem.B.dylib
0x8036a000 - 0x804e5fe7 com.apple.CoreFoundation 6.6.4 (550.42) <C78D5079-663E-9734-7AFA-6CE79A0539F1> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x805dd000 - 0x805ebfe7 libz.1.dylib 1.2.3 (compatibility 1.0.0) <33C1B260-ED05-945D-FC33-EF56EC791E2E> /usr/lib/libz.1.dylib
0x805f0000 - 0x805fcff7 libkxld.dylib ??? (???) <9D8378E0-1C58-EED8-EA00-F4515B8BE7A3> /usr/lib/system/libkxld.dylib
0x80600000 - 0x80646ff7 libauto.dylib ??? (???) <29422A70-87CF-10E2-CE59-FEE1234CFAAE> /usr/lib/libauto.dylib
0x80653000 - 0x807d5fe7 libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <35DB7644-0780-D2AB-F6A9-45F28D2D434A> /usr/lib/libicucore.A.dylib
0x80837000 - 0x808e4fe7 libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <C8925910-B927-968B-4B71-D83A4CEF8646> /usr/lib/libobjc.A.dylib
0x808f8000 - 0x808fbfe7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib
0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <749D24EE-54BD-D74B-D305-C13F5E6C95D8> /usr/lib/dyld
0xb8000000 - 0xb81defff +com.adobe.InDesign 4.0.5.688 (4050) <CC0F32CD-4587-7C83-03D0-9CFE28A58FB6> /Applications/Adobe InDesign CS2/Adobe InDesign CS2.app/Contents/MacOS/Adobe InDesign CS2
0xcde00000 - 0xcdf78fe7 GLEngine ??? (???) <3A6C5513-7428-2242-2892-B429C72343CB> /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
0xcec01000 - 0xced0dff7 libGLProgrammability.dylib ??? (???) <A077BFEA-19C6-9F48-2F36-8E4E55376F49> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dyl ib
0xd0000000 - 0xd0749ff7 com.apple.GeForceGLDriver 1.6.26 (6.2.6) <518182BB-5A3C-5F4C-3A84-17BB8E385BBF> /System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/GeForceGLDriver
0xd09a6000 - 0xd0dabfe7 libclh.dylib 3.1.1 C (3.1.1) <745CBD72-DF1F-EC12-BE51-4EEA9847EADF> /System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/libclh.dylib
0xffff0000 - 0xffff1fff libSystem.B.dylib ??? (???) <4FFBF71A-D603-3C64-2BC6-BFBFFFD562F0> /usr/lib/libSystem.B.dylib
Translated Code Information:
objc[94022]: garbage collection is ON
Rosetta Version: 22.27
Args: /Applications/Adobe InDesign CS2/Adobe InDesign CS2.app/Contents/MacOS/Adobe InDesign CS2 -psn_0_11086482
Exception: EXC_BAD_ACCESS (0x0001)
Thread 0: (0xb02a2d74, 0xb815a8ff)
0x985aaa78: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framew ork/Versions/A/CarbonCore : _MPWaitOnSemaphore + 40
0x01039f90: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE : ACESemaphoreList::Wait(unsigned long) + 36
0x0103a1dc: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE : ACEMPThread::Task() + 76
0x01039ba0: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE : _TaskGlue + 28
0x985ab9c4: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framew ork/Versions/A/CarbonCore : _PrivateMPEntryPoint + 100
0x94f49348: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x985aaabc ctr: 0x94ea8bc0
r00: 0xffffffda r01: 0xf0284d20 r02: 0x02a182c0 r03: 0x00005a03
r04: 0x7fffffff r05: 0x00000000 r06: 0x00000000 r07: 0x00000000
r08: 0x00000000 r09: 0x4d555458 r10: 0x97f6801c r11: 0xa0711694
r12: 0x94ea8bc0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x00000000 r26: 0x00000000 r27: 0x00000000
r28: 0x00000000 r29: 0x7fffffff r30: 0x00000000 r31: 0x985aaa5c
Thread 1: (0xb0428e34, 0xb815a8ff)
0x9502cac8: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
0x9502b1b4: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
0x94f49348: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x9502cae0 ctr: 0x94ea8bc0
r00: 0xffffffda r01: 0xf0407dc0 r02: 0x00000000 r03: 0x00002703
r04: 0x00000040 r05: 0x3b9ab440 r06: 0x00000020 r07: 0x00000000
r08: 0x3b9ab440 r09: 0x00000000 r10: 0x3b9ab440 r11: 0xa0711694
r12: 0x94ea8bc0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0xa07177cc r22: 0xa07177c0 r23: 0xa07177c8
r24: 0x0002309e r25: 0xf6e9f678 r26: 0xa071750c r27: 0x00000040
r28: 0x0000000f r29: 0x224d3440 r30: 0xa07177a0 r31: 0x9502c9d8
Thread 2: (0xb019e84c, 0xb815aa8b)
0x00000000: No symbol
0x985eb504: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framew ork/Versions/A/CarbonCore : _TS_exception_listener_thread + 128
0x94f49348: /usr/lib/libSystem.B.dylib : __pthread_body + 40
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x94ea9284 ctr: 0x94ea8b50
r00: 0xffffffe1 r01: 0xf0182df0 r02: 0xa071c4d0 r03: 0x03001e00
r04: 0x00000002 r05: 0x00000000 r06: 0x00000054 r07: 0x00004e0b
r08: 0x00000000 r09: 0x00000000 r10: 0x03800000 r11: 0xa0711190
r12: 0x94ea8b50 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x03001e00 r23: 0x00000000
r24: 0x00000054 r25: 0x00004e0b r26: 0x00000000 r27: 0x00000000
r28: 0x00000002 r29: 0x00000002 r30: 0x00000000 r31: 0x985eb48c
Thread 3: (0xb04aae34, 0xb815a8ff)
0x9502cac8: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
0x9502b1b4: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
0x94f49348: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x9502cae0 ctr: 0x94ea8bc0
r00: 0xffffffda r01: 0xf0488dc0 r02: 0x00000000 r03: 0x00002703
r04: 0x00000040 r05: 0x3b9ab9b8 r06: 0x00000020 r07: 0x00000000
r08: 0x3b9ab9b8 r09: 0x00000000 r10: 0x3b9ab9b8 r11: 0xa0711694
r12: 0x94ea8bc0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0xa07177cc r22: 0xa07177c0 r23: 0xa07177c8
r24: 0x000230a3 r25: 0x0886686b r26: 0xa071750c r27: 0x00000040
r28: 0x0000000f r29: 0x224d39b8 r30: 0xa07177a0 r31: 0x9502c9d8
Thread 4: (0xba8cfbcc, 0xb815ac81)
0x9140b4e4: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : ___CFSocketManager + 872
0x94f49348: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x9140b598 ctr: 0x94f0969c
r00: 0x0000005d r01: 0xf0592a90 r02: 0xa01ab184 r03: 0x00000040
r04: 0x40600010 r05: 0x40600000 r06: 0x00000000 r07: 0x00000000
r08: 0x00000000 r09: 0xa01bbb80 r10: 0xa06dc800 r11: 0xa01a6448
r12: 0x94f0969c r13: 0xa01b9a3c r14: 0x40600000 r15: 0x00000000
r16: 0xa01bb184 r17: 0x40600010 r18: 0x40600020 r19: 0x914b4d2c
r20: 0x00000000 r21: 0x40600040 r22: 0xf058ae60 r23: 0xa01ba1b8
r24: 0x00000001 r25: 0x00000000 r26: 0x00000040 r27: 0x00000000
r28: 0x00002000 r29: 0xc680b260 r30: 0x00000000 r31: 0x9140b184
Thread 5: (0xb0220d74, 0xb815a8ff)
0x985aaa78: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framew ork/Versions/A/CarbonCore : _MPWaitOnSemaphore + 40
0x01039f90: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE : ACESemaphoreList::Wait(unsigned long) + 36
0x0103a1dc: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE : ACEMPThread::Task() + 76
0x01039ba0: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE : _TaskGlue + 28
0x985ab9c4: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framew ork/Versions/A/CarbonCore : _PrivateMPEntryPoint + 100
0x94f49348: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x985aaabc ctr: 0x94ea8bc0
r00: 0xffffffda r01: 0xf0203d20 r02: 0x02a182b0 r03: 0x00005903
r04: 0x7fffffff r05: 0x00000000 r06: 0x00000000 r07: 0x00000000
r08: 0x00000000 r09: 0x4d555458 r10: 0x97f6801c r11: 0xa0711694
r12: 0x94ea8bc0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x00000000 r26: 0x00000000 r27: 0x00000000
r28: 0x00000000 r29: 0x7fffffff r30: 0x00000000 r31: 0x985aaa5c
Thread 6: (0xb011c84c, 0xb815aa8b)
0x913fa368: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : ___CFRunLoopModeIsEmpty + 160
0x913fea14: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : ___CFRunLoopRun + 2396
0x913ffc64: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFRunLoopRunSpecific + 656
0x913ffec4: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFRunLoopRun + 72
0x91123688: /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopService sPriv : TSystemNotificationTask::SystemNotificationTaskProc(void*) + 556
0x985ab9c4: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framew ork/Versions/A/CarbonCore : _PrivateMPEntryPoint + 100
0x94f49348: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x94ea9284 ctr: 0x94ea8b50
r00: 0xffffffe1 r01: 0xf0101060 r02: 0xa01ba3f4 r03: 0xf010117c
r04: 0x07000006 r05: 0x00000000 r06: 0x00000800 r07: 0x0000b317
r08: 0x00000000 r09: 0x00000000 r10: 0x00000000 r11: 0xa0711190
r12: 0x94ea8b50 r13: 0x00000000 r14: 0x7fffffff r15: 0xffffffff
r16: 0x00023032 r17: 0x86031175 r18: 0xa07186d0 r19: 0x914b3ba8
r20: 0xa01b9a3c r21: 0xf010117c r22: 0xf010117c r23: 0x00000000
r24: 0x00000800 r25: 0x0000b317 r26: 0x00000000 r27: 0x00000000
r28: 0x07000006 r29: 0x07000006 r30: 0x00000000 r31: 0x913fe0c0
Thread 7: Crashed (0xb7fff9d0, 0xb80c5d10)
0x1faea848: ./Document Framework.framework/Versions/A/Document Framework : _GetPlugIn + 362104
0x1faeabbc: ./Document Framework.framework/Versions/A/Document Framework : _GetPlugIn + 362988
0x15cedba4: ./AppFramework.framework/Versions/A/AppFramework : _GetPlugIn + 37412
0x15cee2e8: ./AppFramework.framework/Versions/A/AppFramework : _GetPlugIn + 39272
0x2c192f0c: @executable_path/PublicLib.dylib : CSubject::Change(IDType<ClassID_tag>, IDType<PMIID_tag> const&, void*) + 108
0x47ab45b8: ./DataMerge.framework/Versions/A/DataMerge : _GetPlugIn + 254984
0x47ab4884: ./DataMerge.framework/Versions/A/DataMerge : _GetPlugIn + 255700
0x47ab3198: ./DataMerge.framework/Versions/A/DataMerge : _GetPlugIn + 249832
0x6f6bff60: ./DataMergeUI.framework/Versions/A/DataMergeUI : dyld_stub_binding_helper + 13072
0x6f6c2400: ./DataMergeUI.framework/Versions/A/DataMergeUI : dyld_stub_binding_helper + 22448
0x2b0adfe8: @executable_path/WidgetBinLib.dylib : CActionComponent::DoAction(IActiveContext*, IDType<ActionID_tag>, Point, IPMUnknown*) + 40
0x2cd230f0: ./Actions.framework/Versions/A/Actions : _GetPlugIn + 6176
0x6f6e2b28: ./DataMergeUI.framework/Versions/A/DataMergeUI : _GetPlugIn + 111128
0x15cedba4: ./AppFramework.framework/Versions/A/AppFramework : _GetPlugIn + 37412
0x15cee2e8: ./AppFramework.framework/Versions/A/AppFramework : _GetPlugIn + 39272
0x2c192f0c: @executable_path/PublicLib.dylib : CSubject::Change(IDType<ClassID_tag>, IDType<PMIID_tag> const&, void*) + 108
0x4d01bd94: ./Widgets.framework/Versions/A/Widgets : MDocWindow::GetStandardZoom(Rect*) + 4596
0x4d01bb28: ./Widgets.framework/Versions/A/Widgets : MDocWindow::GetStandardZoom(Rect*) + 3976
0x2b00b6e4: @executable_path/WidgetBinLib.dylib : GenericButtonEventHandler::TiggerControlData() + 100
0x2b00afb8: @executable_path/WidgetBinLib.dylib : ControlEventHandler::LButtonUp(IEvent*) + 456
0x2c1d68c4: @executable_path/PublicLib.dylib : CEventDispatcher::DispatchToEventHandlers(IEvent*) + 356
0x2c1d694c: @executable_path/PublicLib.dylib : CEventDispatcher::DispatchEvent(IEvent*, IEvent::SystemHandledState) + 28
0x15f8982c: ./Application UI.framework/Versions/A/Application UI : _GetPlugIn + 371404
0x15f86f2c: ./Application UI.framework/Versions/A/Application UI : _GetPlugIn + 360908
0x907b6640: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Ver sions/A/HIToolbox : DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1524
0x907b6ffc: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Ver sions/A/HIToolbox : SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 456
0x907b733c: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Ver sions/A/HIToolbox : _SendEventToEventTarget + 72
0x907b27f8: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Ver sions/A/HIToolbox : ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 1084
0x907b6a78: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Ver sions/A/HIToolbox : DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2604
0x907b6ffc: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Ver sions/A/HIToolbox : SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 456
0x907b733c: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Ver sions/A/HIToolbox : _SendEventToEventTarget + 72
0x15cc97f4: ./AppFramework.framework/Versions/A/AppFramework : dyld_stub_binding_helper + 3124
0x15ce851c: ./AppFramework.framework/Versions/A/AppFramework : _GetPlugIn + 15260
0x00002c58: No symbol
0x000024fc: No symbol
0x00002370: No symbol
0xa8f7ffbf: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x1faea848 ctr: 0x94f91e60
r00: 0x1faea848 r01: 0xbfffc920 r02: 0x00000000 r03: 0x00000000
r04: 0x00000048 r05: 0x00000000 r06: 0x0000000b r07: 0x00000001
r08: 0x00002cb0 r09: 0x014aca80 r10: 0x00e01928 r11: 0xa0e410f8
r12: 0x94f91e60 r13: 0x00000000 r14: 0x00000000 r15: 0xcddb2d70
r16: 0x00000000 r17: 0xcdd5b730 r18: 0xd3311360 r19: 0xa01a73fc
r20: 0xa01b7f18 r21: 0xa01b7f48 r22: 0xffffffff r23: 0x00000000
r24: 0x1f9ed360 r25: 0xbfffd358 r26: 0x0000000a r27: 0xcdd70680
r28: 0xcdd81e40 r29: 0x00000000 r30: 0xcdd70120 r31: 0x1faea3d4
Thread 8: (0xb0324d74, 0xb815a8ff)
0x985aaa78: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framew ork/Versions/A/CarbonCore : _MPWaitOnSemaphore + 40
0x01039f90: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE : ACESemaphoreList::Wait(unsigned long) + 36
0x0103a1dc: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE : ACEMPThread::Task() + 76
0x01039ba0: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE : _TaskGlue + 28
0x985ab9c4: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framew ork/Versions/A/CarbonCore : _PrivateMPEntryPoint + 100
0x94f49348: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x985aaabc ctr: 0x94ea8bc0
r00: 0xffffffda r01: 0xf0305d20 r02: 0x02a182d0 r03: 0x00005b03
r04: 0x7fffffff r05: 0x00000000 r06: 0x00000000 r07: 0x00000000
r08: 0x00000000 r09: 0x4d555458 r10: 0x97f6801c r11: 0xa0711694
r12: 0x94ea8bc0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x00000000 r26: 0x00000000 r27: 0x00000000
r28: 0x00000000 r29: 0x7fffffff r30: 0x00000000 r31: 0x985aaa5c
Thread 9: (0xb009adf8, 0xb815acc0)
0x9502b4dc: /usr/lib/libSystem.B.dylib : __dispatch_mgr_invoke + 228
0x9502aec0: /usr/lib/libSystem.B.dylib : __dispatch_queue_invoke + 308
0x9502b050: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread2 + 372
0x9502b18c: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 76
0x94f49348: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x9502b4a4 ctr: 0x94eec7e4
r00: 0x0000016b r01: 0xf0080bb0 r02: 0x00000003 r03: 0x00000004
r04: 0x00000000 r05: 0x00000000 r06: 0xf0080d0c r07: 0x00000001
r08: 0xf0080d28 r09: 0x00000000 r10: 0x00000003 r11: 0xa0710530
r12: 0x94eec7e4 r13: 0x10624dd3 r14: 0x9507ab04 r15: 0xf0080c0c
r16: 0xf0080c8c r17: 0xa072b400 r18: 0xf0080d28 r19: 0xa0725570
r20: 0xa0726570 r21: 0xf0080d0c r22: 0xa07254f0 r23: 0xa0725470
r24: 0xa072b400 r25: 0x00000000 r26: 0xa071762c r27: 0x00000000
r28: 0xa0717604 r29: 0xa071733c r30: 0xf0080d28 r31: 0x9502b400
Thread 10: (0xb052ce34, 0xb815a8ff)
0x9502cac8: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
0x9502b1b4: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
0x94f49348: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x9502cae0 ctr: 0x94ea8bc0
r00: 0xffffffda r01: 0xf0509dc0 r02: 0x00000000 r03: 0x00002703
r04: 0x00000040 r05: 0x3b9ab6bf r06: 0x00000020 r07: 0x00000000
r08: 0x3b9ab6bf r09: 0x00000000 r10: 0x3b9ab6bf r11: 0xa0711694
r12: 0x94ea8bc0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0xa07177cc r22: 0xa07177c0 r23: 0xa07177c8
r24: 0x000230a3 r25: 0x587f1505 r26: 0xa071750c r27: 0x00000040
r28: 0x0000000f r29: 0x224d36bf r30: 0xa07177a0 r31: 0x9502c9d8
Thread 11: (0xb03a6d78, 0xb815a8c8)
0x94f45a34: /usr/lib/libSystem.B.dylib : __pthread_cond_wait + 704
0x51c6a448: ./TINthread.dylib : ThreadUtils::ConditionVariable::Wait(ThreadUtils::MutualExclusion&) + 24
0x51c65708: ./TINthread.dylib : ThreadUtils::ThreadPool::Dispatcher() + 180
0x51c651a4: ./TINthread.dylib : ThreadUtils::ThreadPool::ThreadProc(void*) + 20
0x94f49348: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x94f45b3c ctr: 0x94ea8bb0
r00: 0xffffffdb r01: 0xf0386d30 r02: 0x00000001 r03: 0x00007d03
r04: 0x00007e03 r05: 0x00000028 r06: 0x00000030 r07: 0x00007c03
r08: 0x00000000 r09: 0x00000001 r10: 0x00000000 r11: 0xa0711698
r12: 0x94ea8bb0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x00000000 r26: 0xa071871c r27: 0x00000000
r28: 0x4ff07270 r29: 0x00000000 r30: 0x4ff072d0 r31: 0x94f45780
Model: MacPro4,1, BootROM MP41.0081.B07, 8 processors, Quad-Core Intel Xeon, 2.26 GHz, 6 GB, SMC 1.39f5
Graphics: NVIDIA GeForce GT 120, NVIDIA GeForce GT 120, PCIe, 512 MB
Memory Module: global_name
Bluetooth: Version 2.3.8f7, 2 service, 19 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: NVIDIA GeForce GT 120, Display, Slot-1
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: Hitachi HDE721064SLA360, 596.17 GB
USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0xfa200000
USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0220, 0xfa220000
USB Device: Microsoft 3-Button Mouse with IntelliEye(TM), 0x045e (Microsoft Corporation), 0x0053, 0x1d100000
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x5a100000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8215, 0x5a110000
FireWire Device: built-in_hub, Up to 800 Mb/secTry KERN_PROTECTION_FAILURE at 0x0000000000000000 and read the WHOLE thread.
Maybe you are looking for
-
hi I have package with a procedure naming do_job which have to create a job using dbms_job.submit the owner of this package is a user named "HOL" , but when I try to run this package (I create a public synonym for the package and I gave execute grant
-
Oracle Forms - How can I create a Data Block with query
Dear friends I have a question, I couldn't do this.. I have a sql query, I want to show the datas of the query.. How can I do this. ? Data Block Wizard wants a table, view or stored procedure, but I have a query, how can I create a data block with my
-
Hello, I don't know why, but in the following thread Re: how i can disable MONITORING temp tables the italic and code tags were not taken in account into the output. Nicolas. ok, solved, sorry, the tag end was not correct. Message was edited by: N. G
-
Capture the Popup window action
Hi, I have a requirement when i click 'yes' on popup window i need to save the data. For that i need to capture the fctcode of save. Below is the sample code... Data: context_node type ref to if_wd_context_node. data: lr_popup type ref to if_
-
Hi Guys While runnning the APP sometimes in cheques payments although the payment document has been posted the check register is not getting updated. Sometimes out of 100 payments, some, say 10 cheque payments are not getting updated. As a result of