FrameMaker 12 Save as XML crash

Has anyone had any trouble saving as xml in FM12? Using the same structured applications that have worked through framemaker 8, 9, 10 and 11 we now get a crash in Framemaker 12.
The crash doesn't seem to be in our IO client. The last notification we receive is:
notification [13] sparam [TryAlternativeExtensions 0]
Has Framemaker 12 changed anything in this area?
regards,
Colin Clark

Colin,
There were some issues reported during the pre-release with Save As XML. Can you post some more details (and file any FM crash logs by emailing to [email protected] ). I'll alert the engineers to have a look at this thread.

Similar Messages

Error during "Save as XML" - SVG Image

Hi,
I am trying to save the book as XML (File à Save as XML), but its showing the attached error (FMError.PNG). FrameMaker created a error log and am pasting its header contents below.
=== Header Begin ===
Internal Error: 9004, 6920492, 9676798, 0
FrameMaker 9.0.0 for Intel
Build: 9.0p237
Window System: MSWindows
Operating System: Windows NT 6.1 (major.minor.build: 6.1.7600 )
Generated on: Wednesday, September 08, 2010 2:14:40 PM
To file: C:\Users\30088130\AppData\Roaming\Adobe\FrameMaker\9\FrameLog_10.09.08_14.14.40.txt
=== Header End ===
This errors occurs only if SVG images are present on the fm files.
Please help me on this.

I just tested with a small sample SVG file (from here:
http://www.w3schools.com/svg/tryit.asp?filename=ellipse1&type=svg )
and FM didn't crash when I did Save as XML. I put the SVG inside an anchored frame.
Could you test using that specific image and see if you get the crash or whether it's OK?
Unfortunately FM did clip the right side of the image when the image is displayed, and also when the image is saved to XML (it was converted to GIF in the export).
Googling for "svg framemaker" brought up some old Framers list references to other issues with FM's SVG handling.
I also notice that in the maker.ini there is a commented out reference to an SVG import filter in the APIClients section:
;SVG Import=FileToFileGFXImport, SVG, FrameImage, SVG, ORBL, SVG, SVG, filters\svgfilter.dll,all,^.svg
SVG Import=FileToFileGFXImport, SVG, PDF, SVG, ORBL, SVG, SVG, filters\svg2pdf.dll,all,^.svg
What it seems to be changing is that the second line will automatically convert SVG to PDF on import, so
you might try the other filter:
save a backup copy of the maker.ini, open the makier.ini in a text editor, then switch the semi-colon to the next line, save, and test to see whether you get any better results.
Have you been able to successfully export any files with SVG, or does the problem only occur with some files?
Also, exactly how are you importing the problem SVG file into FM? Referenced or embedded, is it on a body page, master page, in an anchored graphic frame or not, etc? Do you know what application was used to create the SVG files?
Sheila

FM Variables renamed and duplicated after save to XML

Hello again,
I am also encountering an issue where saving structured docs as XML results in duplication and renaming of variables. For example, in a particular document I have the name of the web service inserted as a variable 4 times throughout the piece. After I save to XML, the variable is renamed fmvar1, fmvar2, fmvar3, and fmvar4. So, when I open the doc again, instead of having 1 variable in 4 locations, I now have 4 variables in 4 locations.
Is this something I should expect, as there is no legitimate way to tell the XML doc (or for FM to pass that information on) that it is the same variable, used in 4 places?
Regards,
Hannah

Hannah,
You don't mention the name of your FrameMaker variable. I suspect that it contains a space or other special character that is not permitted in an XML name.
FrameMaker writes variables to XML as general entity references. If a variable name is a valid MXL name, by default it uses the variable name as the entity name. Multiple references to such an entity can occur. If not, it names the variable fmvar# where # is an integer. In this case, you are correct that it generates a different entity for each occurrence of the variable. I also consider this proliferation of general entities to be a bug.
You can change the default behavior with a r/w rule in the form:
entity "twowords" is fm variable "two words";
In your case, thus, you have at least 3 choices:
1) Live with the multiple entities
2) Rename the variable to something that can be used as an entity name
3) Add a r/w rule for each variable in any document that causes this problem
--Lynne

Automate Save As XML

I have a bunch of PDFs that I want to save as XML, is there any way to do this automatically? Without having to open them all up and go to File -> Save As -> XML.
Thanks

I am trying to solve the exact same problem. What is batch sequencing? I need to be able to run a command to automatically save a set of framemaker files as xml.
Thanks!

Problem Working With Framemaker 9 Dita XML Files in Framemaker 10

I just upgraded to Framemaker 10. I am encountering a number of problems when I try to work with my Dita XML help topics, which were last saved in Framemaker 9 format.
1. Using the Default Dita Template
When I open one of my documents in Framemaker 10, the Dita 1.2 template ditabase.fm is automatically applied. Everything seems fine. But then when I convert the XML to Eclipse help (which is essentially html, so we're going from XML to HTML) using Dita Open Toolkit ant scripts, I see this message:
[pipeline] [DOTJ013E][ERROR] Failed to parse the referenced file 'html\c_licensing.xml' due to below exception. Please correct the reference base on the exception message.
[pipeline] c_licensing.xml Line 25:Attribute "xmlns:ditaarch" must be declared for element type "dita".
I then opened the xml file in a text editor, and I saw this on line 25:
<dita xmlns:ditaarch = "http://dita.oasis-open.org/architecture/2005/">
Line 25 looks fine to me. Am I missing something?
2. Switching to a 1.1 Dita Template
I tried to work around the above problem. In Framemaker, I tried to set a different structured application as the default one. I closed all files and chose the default Dita 1.1 structured application (it defaults to the Dita 1.1. Composite app.)
Then I tried to open my file: I got this message inside Framemaker:
"Validation of XML failed. Continue?
Error at [FILE PATH], line 25, char 72, Message: Attribute '{http://www.w3.org/2000/xmlns/}ditaarch' is not declared for element 'dita'
Sounds familiar, doesn't it?
I switched from the default Dita 1.1. Composite structured application to the Dita 1.1. Topic structured application. Then I dirtied the source file and saved it. The messages I got in FrameMaker log window included the one above, plus I got a variety of Unknown Element messages, things like this:
Unknown element dita,
unknown element concept,
various attributes are not declared for concept,
unknown element conbody.
If I switch back to the Dita 1.1 Composite application all of these messages diappear except for this one:
Attribute '{http://www.w3.org/2000/xmlns/}ditaarch' is not declared for element 'dita'
My ant conversion scripts from the Dita Open Toolkit are still unable to process this file. They give the same message as is listed in (1) above and the file is not converted to HTML.
Can anyone help me with this problem? I've also posted this question to the Dita Users Group on Yahoo Groups. If I get an answer in one place, I'll post it in the other.
Thanks,
Nina P.

I really appreciate all the help you are providing with this, Scott. I tried your latest suggestions. Here's what happened:
Application Mappings:
I figured out how to add my "BigPage" structured application to the Applications Mappings dialog. I made a new "BigPage" mapping type, then figured out the non-intuitive part: how to add my individual BigPage topic types to it. I closed and reopened FrameMaker opened my test document, and, as before (before I did the application mappings) I saw my BigPage applications listed in the Structure Tools > Set Structured Application drop-down. I selected the appropriate application (in this case it was DITA1.1-BigPage-Reference-FM and clicked the "Set" button.
It is at this point in Framemaker 9 (and also once, in FrameMaker 10, early in this process, but I haven't been able to replicate it since) that the page size would change to tabloid size, indicating that the document was using the template from the BigPage reference structured application, not the regular DITA1.1 reference application. But this did not happen.
I tried saving the document, closing it, and reopening it. Once again the default structured application assigned to that document was "reset" to DITA1.1-Reference-FM. But the fact that the page size did not immediate refresh to tabloid size told me that although I did select the BigPage application in the drop-down, it wasn't being applied.
Public IDs:
The public ID in my test reference XML file is: <!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd" [
The four public IDs in the DITA1.1-BigPage-Reference-FM entry in structapps.fm (in the Entity Locations section) are:
-//OASIS//DTD DITA Reference//EN
-//IBM//DTD DITA Reference//EN
-//OASIS//DTD DITA Composite//EN
-//IBM//DTD DITA Composite//EN
Do you see anything wrong with the above? .
Directory Structure:
Maybe I cloned the application incorrectly? Here's what I did:
1. In C:\Program Files (x86)\Adobe\AdobeFrameMaker10\Structure\xml, I copied the folder called DITA and pasted it into the same directory. I renamed this folder DITA-BigPage
2. Inside DITA-BigPage, I opened the app folder. Inside each subfolder in app, DITA-Reference-FM, for example, I opened the edd file in Framemaker. In this case, the edd file name was reference.edd.fm.
3. I edited the top line of reference.edd.fm. It originally said:
Structured Application: DITA1.1-Reference-FM.
I changed it to say:
Structured Application: DITA1.1-BigPage-Reference-FM
4. I saved the EDD file. Then I opened the template file in the same folder. It was called: reference.template.fm.
5. In reference.template.fm, I first changed my page size: Format Menu > Page Layout > Page Size > Tabloid > Set.
6. Then I imported the element definitions from the corresponding EDD file: File > Import > Element Definitions > reference.edd.fm > Click Import > Click OK to dismiss verification message.
7. I repeated the above process for all topic-type folders. For the maps types, I did not change the page size, as these will never display as topics in my online help. I did nothing to the dtd folder.
8. Once all this was done, I opened structapps.fm. I did the following to all Dita1.1 elements in the structure tree.
Selected the Dita 1.1 XMLApplication element, for instance, the one named Dita1.1-Reference-FM, copied it, and pasted it underneath the original element.
The original first few lines in the clone looked like this:
Application Name: DITA1.1-Reference-FM
      Template:              $STRUCTDIR\xml\DITA\app\DITA-Reference-FM\reference.template.fm
      DTD:                       $STRUCTDIR\xml\DITA\app\dtd\reference.dtd
      Read/write Rules: $STRUCTDIR\xml\DITA\app\DITA-Reference-FM\reference.rules.fm
      DOCTYPE:              reference
I changed these lines to look like this, using your suggestion to create a variable for the first part of the URLs to enable speed and accuracy:
       Application Name:      DITA1.1-BigPage-Reference-FM
               Template:                    $STRUCTDIR\xml\DITA-BigPage\app\DITA-Reference-FM\reference.template.fm
               DTD:                            $STRUCTDIR\xml\DITA-BigPage\app\dtd\reference.dtd
               Read/write Rules:        $STRUCTDIR\xml\DITA-BigPage\app\DITA-Reference-FM\reference.rules.fm
               DOCTYPE:                    reference
I also changed the "Filename" URLs in the "Entity Locations" section of this XMLApplication clone from $STRUCTDIR\xml\DITA\app\ to $STRUCTDIR\xml\DITA-BigPage\app\. Applying the "BigPage" variable I'd created for this purpose made this go quickly.
Finally, after this didn't work the first few times I tried it, I got suspicious that the structapps.fm file in my AppData folder (in my case, it was in the Roaming subfolder under the usual Adobe directories) was overriding the modified structapps.fm file in the Framemaker program directory so I replaced the one in AppData (it had all the original settings) with my modified version. This had no effect, unfortunately.
That was my process. After doing the above, the Dita1.1-BigPage applications all listed in the Set Structured App drop-down. They just didn't work,when applied to my XML documents. Nor did the application "remember" what structured application I had set when I opened a new xml document or closed/reopened the current document or closed/reopened the application. Did I place the directories correctly for Framemaker 10? This is the way I did it for FrameMaker 9 and it worked successfully.
As much as I'd love to solve this mystery, I've thought of a workaround I can fall back on that doesn't involve using a cloned application. I will change the page size of a few of the original Dita1.1 sturctured application templates to tabloid size, but leave the Topic structured application at letter size. I'll then apply the Topic structured application to my PDFs and use the others for my help topics. I'll set this up now. If this doesn't work, then I'll know there's a much bigger problem at the base of this, perhaps even something to do with changing page sizes in templates.

How can I save a XML file with JAXP1.1?

Dear All.
I write a program to create XML file with DOM model, but I can't know how to save it? My environment is JAXP1.1 and JDK1.3.1,I has been required not use other XML parser toolkits,only JAXP1.1.
How can I do? thank you.
Many person give me a idea the com.sun.xml.tree.XmlDocument, but I can't find the class in API document or JAXP1.1's packages. why?
what is it? How can i use it?
thank you very much.

The way to save an XML Document is using a Transformer.
To have access to a transformer use the packages :
import javax.xml.transform.*;
import javax.xml.transform.dom.*;
import javax.xml.transform.stream.*;
Then for saving your Document Object (named dXml) get a Transformer Object with the TransformerFactory Object :
TransformerFactory tf = TransformerFactory.newInstance();
Transformer t = tf.newTransformer();
Now you have got your Transformer Object, to save your Document Object use the method :
Document dXml = getMyDocument(); // this is your Document Object.
OutputStream osSave = getMySaveStream(); // this the OutputStream you need to save your Document.
try
t.transform(new DomSource(dXml), new StreamResult(new OutputStreamWriter(osSave)));
finally
osSave.close();
And your Document was now saved.

Save whole XML file in SQL table field

Hi All,
I want to save whole XML message in sql table field which is with datatype XML(.).. how can i achieve this.
Thanks in advance.
2Venture2

I did a prototype to do what you are asking. I actually haven't inserted into the xml data type in SQL Server before, so I was curious if that added any complexity. I'll just go through the mapping pieces and assume that you can easily find documentation
on how to insert data into SQL Server using the Add Generated Items --> Consume Adapter Service function.
The interesting piece was writing the map. I used a simple PO schema. My sample table was XmlRepository with a ID column, RepositoryID, and the RawXml field.
The script is an inline XSLT script that is as follows:
<xsl:element name="ns3:RawXml">
<xsl:text disable-output-escaping="yes"><![CDATA[</xsl:text>
<xsl:copy-of select="/" />
<xsl:text disable-output-escaping="yes">]]></xsl:text>
</xsl:element>
The questoin right off is why the CDATA? Well, since the value of the RawXml element that needs to be inserted into SQL Server is XML data, it has to be wrapped in a CDATA tag. Otherwise, the XML data gets validated and will not properly make it to the SQL
Server. You can try it and see what I mean. Don't worry, the CDATA gets stripped before the XML gets written to the table.
The interesting piece are the xsl:text elements, which manually create a CDATA wrapper for the XML that ends up in the RawXml field. Apparently, the normal Grid Property for creating CDATA output doesn't work in conjunction with the xsl:copy-of function.
That tripped me up for a while!
What the map outputs is a document that looks like the following:
<ns0:Insert xmlns:array="http://schemas.microsoft.com/2003/10/Serialization/Arrays" xmlns:ns3="http://schemas.microsoft.com/Sql/2008/05/Types/Tables/dbo" xmlns:ns0="http://schemas.microsoft.com/Sql/2008/05/TableOp/dbo/XmlRepository">
<ns0:Rows>
<ns3:XmlRepository>
<ns3:RawXml>
<![CDATA[<ns0:PurchaseOrder xmlns:ns0="http://XmlRepositoryDemo.PurchaseOrder">
<PONumber>PONumber_0</PONumber>
<CustomerNumber>CustomerNumber_0</CustomerNumber>
<PODate>PODate_0</PODate>
<Items>
<Item>
<ProductID>ProductID_0</ProductID>
<Quantity>Quantity_0</Quantity>
<Price>Price_0</Price>
</Item>
</Items>
</ns0:PurchaseOrder>]]>
</ns3:RawXml>
</ns3:XmlRepository>
</ns0:Rows>
</ns0:Insert>
The map can be called from a simple Orchestration, or even a messaging-only scenario, and sent across the wire in a request/reply as you would for normally sending data to SQL Server.
I hope this helps. It ended up being more interesting than I expected!

I installed the latest Acrobat Reader (11) and every time I try to do a Save As, it crashes the entire Adobe program closing all files. I tried uninstalling and re-installing and it still crashes.

I installed the latest Acrobat Reader (11) and every time I try to do a Save As, it crashes the entire Adobe program closing all files. I tried uninstalling and re-installing and it still crashes.

Hi Bryan ,
It happens when you save it as an Adobe PDF or a normal PDF?
Happens with all the files or any specific one?
What exact version of Acrobat are you using?
Try updating it to the latest one if it is an older one.
You may also want to uninstall and re install it to check.
Let us know how it goes.
Regards
Sukrit Dhingra

FrameMaker 11 trial version crashing on save and cross-reference insertion

Hi everyone,
I've recently started a new position. My prior background was heavily DITA, and I'd describe my FrameMaker experience as late beginner or early intermediate. The new position uses FM exclusively though, so I've been on a steep learning curve lately.
I'm using the trial version of FrameMaker 11, downloaded about two weeks ago, until the PO for my full FM 11 license is processed. I'm working in book and document files that have been upgraded, I believe, from FM 9 to FM 10 and then from FM 10 to FM 11. All of my colleagues are still using FM 10, with a mind to upgrade to FM 11 in the spring as our new budget comes through (I am, so to speak, the FM 11 guinea pig for the group).
My workstation is a brand new HP Elitebook laptop running Windows 7 64-bit (I believe our IT department downgraded it from Windows 8). Windows is fully up-to-date. My trial version of FM 11 is 11.0.1.382 and also up-to-date as of this message.
My issue: FM 11 randomly crashes several times a week, sometimes once a day or so, sometimes when I try any of the following:
Saving all files in a book (using Shift + the File menu command)
Saving individual document files (generally using the Save icon in the tool bar)
Attempting to insert a cross-reference (placing the insertion point within the document, then opening the Cross-Reference tool in the right-hand side bar)
The crash takes the appearance of FM freezing for several seconds, then the dreaded message window opening with the words "FrameMaker has detected a serious error and must quit", with columns of error codes below.
I've googled and binged and not found anything for this issue in FM 11, so I thought I'd post here. I have tried the following, based on somewhat similar discussions I've seen for crashes in earlier versions of FM)
Mif-washing the files
Working in the Structured FrameMaker interface instead of the Unstructured
Neither of these has worked. FM 11 trial continues to crash. It doesn't happen often; I'd say that I'm able to successfully able to perform the above tasks 20 times or so, with the crash on the 21st. But on a busy day, that's a few crashes a day.
To mitigate damage, I have autosave set to every two minutes and gotten in the habit of only having one or two documents open, instead of all in a book, to minimize the number of recovery files I need to process.
After one of the initial crashes, I did as Adobe asked and forwarded the crash report to them for troubleshooting.
My colleagues are watching all this very closely, and my troubles might influence our decision to upgrade from FM 10 to FM 11. So any insight into this issue would be appreciated!
Cheers,
Eric

Eric,
The multitude of unesolved x-refs may due to the font issues when updating the book. During an update, if the files aren't open, FM tries to open them in the background but if it encounters an error like a missing font, it skips the file and then any x-refs to that file are unresolved. This can cascade to make things look really worse than they are.
What is your default printer when you start FM? It should be the Adobe PDF prnter instance. If not, then you might want to insatll the Sundorne SetPrint utility (http://www.sundorne.com/FrameMaker/Freeware/setPrint.htm) thta will automatically set this for your FM sessions only.
One other place where fonts can hide is in table definitions. The catalog stores the font information (and not just the explicit paratag) of the cells in the header and first row. As Jeff mentions, you need to check the MIF file in detail. An excellent tool for quickly browsing your MIF is Graham Wideman's Mifbrowse (http://www.wideman-one.com/gw/tech/framemaker/mifbrowse.htm).

Internal Error: 8004, 4867936, 4920984, 4921436 while attempting to save as XML

Hi,
I get the following error while trying to save fm files as XML.
=== Header Begin ===
Internal Error: 8004, 4867936, 4920984, 4921436
FrameMaker 8.0.0 for Intel
Build: 8.0p266
Window System: MSWindows
Operating System: Windows NT 6.1 (major.minor.build: 6.1.7600 )
Generated on: Tuesday, November 26, 2013 2:01:40 PM
To file: c:\program files\adobe\framemaker8\FrameLog_13.11.26_14.01.40.txt
=== Header End ===
-ramesh

Yes .. definitely get the latest FM8 patch, that may solve the problem.
http://www.adobe.com/support/downloads/product.jsp?product=22&platform=Windows
However, if this is a structured document, you should also be sure to validate (Element > Validate) the file before saving. Also check for graphics that are referenced from a reference page, and you may want to delete any cross-refs that aren't resolved (or resolve them). FM can crash for a variety of reasons when saving to XML, anything that's slightly amiss is likely to cause a problem.
Cheers,
...scott

FrameMaker loses formatting during crashes

I recently upgraded from FrameMaker 8 to 10, and I have noticed that Frame 10 has a charming habit of losing formatting when it crashes. So for example, if a paragraph tag is supposed to be bold, all text with that tag will no longer be bolded after the crash. The paragraphs are still tagged correctly, but I have to go back and apply the "Default Font" character tag to each paragraph with mangled formatting. It's incredibly aggravating, and I usually just revert to an older version of the document (and copy any new or changed material over), but obviously this is inefficent and will be error-prone in the long run. Just out of curiosity, has anyone seen this bad behavior?
I don't know if it matters, but I am using Windows XP Professional 32-bit, and all of my files were created in Frame 8.

1. Same system for FM8 and 10 -- but what OS & SP? -- always useful for us to know when trying to track down "issues".
4. Reboot after crashes. I always reboot after crashes, to my way of thinking there's just too much chance of something critical to operation getting clobbered during the crash.
5. Event viewer. I would also check events just prior to FM's crash to see whether there are any that seem "suspiciously close". For example, do you also use any Office 2010 apps? If so, there's a known crash in Word and Outlook that involves a file called "usp10.dll" which is the Uniscribe (unicode) font display module that you might see in the Event log. There's some sort of incompatibility with Adobe PS fonts, very often with Helvetica but also other PS fonts.
AFAIK FM doesn't apparently use usp10.dll, but seeing as font rendering is so essential to FM it wouldn't surprise me if the crash is also affecting something else font-related that FM does rely on -- e.g. I hear echoes of the still-an-issue MS hotfix for XP, for text missing in PDFs,
Adobe blog: Hotfix for FrameMaker
In theory there's a hotfix issued Jan 21/2011 for the usp10.dll issue, but I have yet to find any corroboration that the issue is indeed fixed.
http://support.microsoft.com/kb/2119612
Error message opening a document in Word 2010: "Microsoft Office Word has encountered a problem and needs to close" USP10.DLL
Oh, and even if you are not using Helvetica or other PS fonts in the documents intentionally, if the docs could possibly have been edited by other folks on other systems or other versions of FM, or where a different printer was selected as the default, or content was copied in from another FM file, then Helvetica could still be in the files, e.g. in the titles on reference pages, or in a table definition (even if there isn't an instance of that table format in the actual doc).
6. consfile.txt (not "console") -- ooops, apologies for sending you on a wild goose chase, my bad.
7. possibly crashes are related to creating PDFs. How do you create PDFs, do you typically use Save As, or do you print to a PS file and then distill? The distinction has often been critical in previous FM versions.
ick, removed big formatting: Sheila Carlisle

Bridge CS4 attempt to Refresh Preview or Save output causes crash in Mac OS 10.8.2

Ever since installing Mountain Lion, I can no longer create contact sheets in Adobe Bridge CS4, which I was always able to do before installing ML. As soon as I press "Refresh Preview," or just try to SAVE the Output (PDF) without refreshing the preview, Bridge crashes with the report below. This is on a MacPro 2.66 GHz Quad-Core Intel Xeon with 20 MB RAM, OS 10.8.2. Ideas gratefully accepted!
Process:
Adobe Bridge CS4 [36715]
Path:
/Applications/Adobe Bridge CS4/Adobe Bridge CS4.app/Contents/MacOS/Adobe Bridge CS4
Identifier:
com.adobe.bridge3
Version:
3.0.0.464 (3.0.0.464)
Code Type:
X86 (Native)
Parent Process: launchd [255]
User ID:
501
Date/Time:
2012-12-10 11:27:27.803 -0800
OS Version:
Mac OS X 10.8.2 (12C60)
Report Version: 10
Interval Since Last Report:
103175 sec
Crashes Since Last Report:
7
Per-App Interval Since Last Report: 702 sec
Per-App Crashes Since Last Report:   4
Anonymous UUID:
B4E344BD-3EB9-8467-8B6F-58F7BB669CFF
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
VM Regions Near 0:
--> __PAGEZERO
0000000000000000-0000000000001000 [
4K] ---/--- SM=NUL /Applications/Adobe Bridge CS4/Adobe Bridge CS4.app/Contents/MacOS/Adobe Bridge CS4
__TEXT
0000000000001000-0000000000cd8000 [ 12.8M] r-x/rwx SM=COW /Applications/Adobe Bridge CS4/Adobe Bridge CS4.app/Contents/MacOS/Adobe Bridge CS4
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   AdobePDFL
0x1f013730 PDFLInitFriends + 192
1   com.apple.carbonframeworktemplate
0x1e140594 Init() + 64
2   com.apple.carbonframeworktemplate
0x1e15efd8 ESInitialize + 120
3   com.adobe.bridge3
0x003a4c90 VCUI_Terminate + 1632106
4   com.adobe.bridge3
0x003a51d5 VCUI_Terminate + 1633455
5   com.adobe.bridge3
0x003a41c3 VCUI_Terminate + 1629341
6   com.adobe.bridge3
0x00371cb4 VCUI_Terminate + 1423246
7   AdobeExtendScript
0x01dbafac ScScript::LiveObjectFunction::propConstruct(ScScript::Object&, ScCore::BasicArray const&, ScScript::ESVariant&, bool) + 328
8   AdobeExtendScript
0x01d8c5b8 ScScript::RealEngine::makeObject(ScScript::ESVariant&, int, ScCore::BasicArray const*, ScScript::Object*) + 532
9   AdobeExtendScript
0x01d236f7 jsOpCall::run(jsRunner&, ScScript::ESVariant&) const + 1461
10 AdobeExtendScript
0x01d2a43d jsOpLocalAssign::run(jsRunner&, ScScript::ESVariant&) const + 601
11 AdobeExtendScript
0x01d24d29 jsOpExprStatement::run(jsRunner&, ScScript::ESVariant&) const + 77
12 AdobeExtendScript
0x01d2f450 jsOpStatements::run(jsRunner&, ScScript::ESVariant&) const + 288
13 AdobeExtendScript
0x01d26c42 jsOpFunction::run(jsRunner&, ScScript::ESVariant&) const + 574
14 AdobeExtendScript
0x01d5b677 jsRunner::run(ScScript::ESVariant&) + 203
15 AdobeExtendScript
0x01d442bc jsFunction::propCall(ScScript::Object&, ScCore::BasicArray const&, ScScript::ESVariant&) + 558
16 AdobeExtendScript
0x01d2372d jsOpCall::run(jsRunner&, ScScript::ESVariant&) const + 1515
17 AdobeExtendScript
0x01d2a43d jsOpLocalAssign::run(jsRunner&, ScScript::ESVariant&) const + 601
18 AdobeExtendScript
0x01d24d29 jsOpExprStatement::run(jsRunner&, ScScript::ESVariant&) const + 77
19 AdobeExtendScript
0x01d2f450 jsOpStatements::run(jsRunner&, ScScript::ESVariant&) const + 288
20 AdobeExtendScript
0x01d26c42 jsOpFunction::run(jsRunner&, ScScript::ESVariant&) const + 574
21 AdobeExtendScript
0x01d5b677 jsRunner::run(ScScript::ESVariant&) + 203
22 AdobeExtendScript
0x01d442bc jsFunction::propCall(ScScript::Object&, ScCore::BasicArray const&, ScScript::ESVariant&) + 558
23 AdobeExtendScript
0x01d2372d jsOpCall::run(jsRunner&, ScScript::ESVariant&) const + 1515
24 AdobeExtendScript
0x01d2a43d jsOpLocalAssign::run(jsRunner&, ScScript::ESVariant&) const + 601
25 AdobeExtendScript
0x01d24d29 jsOpExprStatement::run(jsRunner&, ScScript::ESVariant&) const + 77
26 AdobeExtendScript
0x01d2f450 jsOpStatements::run(jsRunner&, ScScript::ESVariant&) const + 288
27 AdobeExtendScript
0x01d26c42 jsOpFunction::run(jsRunner&, ScScript::ESVariant&) const + 574
28 AdobeExtendScript
0x01d5b677 jsRunner::run(ScScript::ESVariant&) + 203
29 AdobeExtendScript
0x01d442bc jsFunction::propCall(ScScript::Object&, ScCore::BasicArray const&, ScScript::ESVariant&) + 558
30 AdobeExtendScript
0x01d2372d jsOpCall::run(jsRunner&, ScScript::ESVariant&) const + 1515
31 AdobeExtendScript
0x01d331cb jsOpUnary::run(jsRunner&, ScScript::ESVariant&) const + 51
32 AdobeExtendScript
0x01d2b1dc jsOpLogAndOr::run(jsRunner&, ScScript::ESVariant&) const + 232
33 AdobeExtendScript
0x01d28412 jsOpIf::run(jsRunner&, ScScript::ESVariant&) const + 92
34 AdobeExtendScript
0x01d2f450 jsOpStatements::run(jsRunner&, ScScript::ESVariant&) const + 288
35 AdobeExtendScript
0x01d26c42 jsOpFunction::run(jsRunner&, ScScript::ESVariant&) const + 574
36 AdobeExtendScript
0x01d5b677 jsRunner::run(ScScript::ESVariant&) + 203
37 AdobeExtendScript
0x01d442bc jsFunction::propCall(ScScript::Object&, ScCore::BasicArray const&, ScScript::ESVariant&) + 558
38 AdobeExtendScript
0x01d2372d jsOpCall::run(jsRunner&, ScScript::ESVariant&) const + 1515
39 AdobeExtendScript
0x01d331cb jsOpUnary::run(jsRunner&, ScScript::ESVariant&) const + 51
40 AdobeExtendScript
0x01d28412 jsOpIf::run(jsRunner&, ScScript::ESVariant&) const + 92
41 AdobeExtendScript
0x01d2f450 jsOpStatements::run(jsRunner&, ScScript::ESVariant&) const + 288
42 AdobeExtendScript
0x01d26c42 jsOpFunction::run(jsRunner&, ScScript::ESVariant&) const + 574
43 AdobeExtendScript
0x01d5b677 jsRunner::run(ScScript::ESVariant&) + 203
44 AdobeExtendScript
0x01d442bc jsFunction::propCall(ScScript::Object&, ScCore::BasicArray const&, ScScript::ESVariant&) + 558
45 AdobeExtendScript
0x01d2372d jsOpCall::run(jsRunner&, ScScript::ESVariant&) const + 1515
46 AdobeExtendScript
0x01d2a43d jsOpLocalAssign::run(jsRunner&, ScScript::ESVariant&) const + 601
47 AdobeExtendScript
0x01d24d29 jsOpExprStatement::run(jsRunner&, ScScript::ESVariant&) const + 77
48 AdobeExtendScript
0x01d2f450 jsOpStatements::run(jsRunner&, ScScript::ESVariant&) const + 288
49 AdobeExtendScript
0x01d26c42 jsOpFunction::run(jsRunner&, ScScript::ESVariant&) const + 574
50 AdobeExtendScript
0x01d5b677 jsRunner::run(ScScript::ESVariant&) + 203
51 AdobeExtendScript
0x01d442bc jsFunction::propCall(ScScript::Object&, ScCore::BasicArray const&, ScScript::ESVariant&) + 558
52 AdobeExtendScript
0x01d8dc5b ScScript::RealEngine::exec(int, ScScript::Object&, ScScript::Object&, ScCore::BasicArray const&, ScScript::ESVariant&, int) + 825
53 AdobeExtendScript
0x01d8ef14 ScScript::RealEngine::call(ScCore::Variant const&, ScCore::String const&, ScCore::BasicArray const&, ScCore::Variant*, int) + 434
54 AdobeExtendScript
0x01d85ca3 ScScript::Object::notify(ScCore::Message&) + 1399
55 AdobeScCore
0x01e9081f _broadcast(ScCore::Message&, ScCore::TSimpleArray<ScCore::Listener>&) + 155
56 AdobeScCore
0x01e90950 ScCore::Broadcaster::broadcast(ScCore::Message&) const + 162
57 AdobeScCore
0x01e85cd7 ScCore::LiveObject::invoke(ScCore::String const&, ScCore::Array const&, ScCore::Variant&, ScCore::Error*) const + 265
58 com.adobe.bridge3
0x002bbadc VCUI_Terminate + 677302
59 com.adobe.bridge3
0x002bbbd4 VCUI_Terminate + 677550
60 com.adobe.bridge3
0x0033e0c3 VCUI_Terminate + 1211293
61 com.adobe.bridge3
0x0026eefd VCUI_Terminate + 362967
62 com.adobe.bridge3
0x00296cc5 VCUI_Terminate + 526239
63 com.adobe.bridge3
0x0026fcb2 VCUI_Terminate + 366476
64 com.adobe.bridge3
0x00274c3b VCUI_Terminate + 386837
65 com.adobe.bridge3
0x0026f276 VCUI_Terminate + 363856
66 com.adobe.bridge3
0x0026c303 VCUI_Terminate + 351709
67 com.adobe.bridge3
0x0026c3d0 VCUI_Terminate + 351914
68 com.apple.HIToolbox
0x9619ab6b _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
69 com.apple.HIToolbox
0x96022594 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343
70 com.apple.HIToolbox
0x96021980 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
71 com.apple.HIToolbox
0x96035855 SendEventToEventTarget + 88
72 com.apple.HIToolbox
0x960c3a01 SendControlHit(HIView*, OpaqueEventRef*, short, unsigned long) + 303
73 com.apple.HIToolbox
0x960ba1c1 HIView::NotifyControlHit(OpaqueEventRef*, short, unsigned long) + 41
74 com.apple.HIToolbox
0x960ba3d3 HIView::ClickInternal(CGPoint const&, unsigned long, void (*)(OpaqueControlRef*, short), OpaqueEventRef*, bool) + 259
75 com.apple.HIToolbox
0x960ba5dd HIView::ClickSelf(OpaqueEventRef*) + 387
76 com.apple.HIToolbox
0x9602b912 HIView::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 2598
77 com.apple.HIToolbox
0x9619ab6b _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
78 com.apple.HIToolbox
0x96022594 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343
79 com.apple.HIToolbox
0x96021980 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
80 com.apple.HIToolbox
0x9600cfda CallNextEventHandler + 84
81 com.adobe.bridge3
0x0026c491 VCUI_Terminate + 352107
82 com.apple.HIToolbox
0x9619ab6b _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
83 com.apple.HIToolbox
0x96022594 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343
84 com.apple.HIToolbox
0x96021980 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
85 com.apple.HIToolbox
0x96035855 SendEventToEventTarget + 88
86 com.apple.HIToolbox
0x9600f821 HIView::Click(OpaqueEventRef*) + 317
87 com.apple.HIToolbox
0x9600f6d8 HIViewClick + 50
88 com.apple.HIToolbox
0x961a5897 HandleClickAsHIView(OpaqueWindowPtr*, OpaqueEventRef*) + 156
89 com.apple.HIToolbox
0x961a5e46 HandleWindowClick(OpaqueWindowPtr*, Point, short, unsigned long, OpaqueEventRef*) + 494
90 com.apple.HIToolbox
0x961a54a3 HandleMouseEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*) + 826
91 com.apple.HIToolbox
0x9600da38 StandardWindowEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 85
92 com.apple.HIToolbox
0x9619ab6b _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
93 com.apple.HIToolbox
0x96022594 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343
94 com.apple.HIToolbox
0x96021980 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
95 com.apple.HIToolbox
0x96035855 SendEventToEventTarget + 88
96 com.apple.HIToolbox
0x960557b7 ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 2141
97 com.apple.HIToolbox
0x96022a3f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2538
98 com.apple.HIToolbox
0x96021980 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
99 com.apple.HIToolbox
0x96035855 SendEventToEventTarget + 88
100 com.adobe.bridge3
0x003b7313 Mondo::CProcess::Execute(Mondo::CFlags<unsigned long>) + 857
101 com.adobe.bridge3
0x003ab04a Mondo::CExecutable::RunExecute() + 78
102 com.adobe.bridge3
0x003ab0cb Mondo::CExecutable::Run() + 39
103 com.adobe.bridge3
0x0047f94a Mondo::CApplication::Main() + 58
104 com.adobe.bridge3
0x0047ff06 main + 84
105 com.adobe.bridge3
0x00002cc2 start + 258
106 com.adobe.bridge3
0x00002be9 start + 41
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib
0x996829ae kevent + 10
1   libdispatch.dylib
0x9a481c71 _dispatch_mgr_invoke + 993
2   libdispatch.dylib
0x9a4817a9 _dispatch_mgr_thread + 53
Thread 2:
0   libsystem_kernel.dylib
0x996820ee __workq_kernreturn + 10
1   libsystem_c.dylib
0x922a904c _pthread_workq_return + 45
2   libsystem_c.dylib
0x922a8e19 _pthread_wqthread + 448
3   libsystem_c.dylib
0x92290cca start_wqthread + 30
Thread 3:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab220 _pthread_cond_wait + 833
2   libsystem_c.dylib
0x923310a1 pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore
0x95478492 TSWaitOnCondition + 128
4   com.apple.CoreServices.CarbonCore
0x9547868e TSWaitOnConditionTimedRelative + 146
5   com.apple.CoreServices.CarbonCore
0x953c4b9b MPWaitOnQueue + 261
6   AdobeACE
0x0149638d 0x1465000 + 201613
7   AdobeACE
0x01495d85 0x1465000 + 200069
8   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
9   libsystem_c.dylib
0x922a6557 _pthread_start + 344
10 libsystem_c.dylib
0x92290cee thread_start + 34
Thread 4:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab220 _pthread_cond_wait + 833
2   libsystem_c.dylib
0x923310a1 pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore
0x95478492 TSWaitOnCondition + 128
4   com.apple.CoreServices.CarbonCore
0x9547868e TSWaitOnConditionTimedRelative + 146
5   com.apple.CoreServices.CarbonCore
0x953c4b9b MPWaitOnQueue + 261
6   AdobeACE
0x0149638d 0x1465000 + 201613
7   AdobeACE
0x01495d85 0x1465000 + 200069
8   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
9   libsystem_c.dylib
0x922a6557 _pthread_start + 344
10 libsystem_c.dylib
0x92290cee thread_start + 34
Thread 5:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab220 _pthread_cond_wait + 833
2   libsystem_c.dylib
0x923310a1 pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore
0x95478492 TSWaitOnCondition + 128
4   com.apple.CoreServices.CarbonCore
0x9547868e TSWaitOnConditionTimedRelative + 146
5   com.apple.CoreServices.CarbonCore
0x953c4b9b MPWaitOnQueue + 261
6   AdobeACE
0x0149638d 0x1465000 + 201613
7   AdobeACE
0x01495d85 0x1465000 + 200069
8   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
9   libsystem_c.dylib
0x922a6557 _pthread_start + 344
10 libsystem_c.dylib
0x92290cee thread_start + 34
Thread 6:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab220 _pthread_cond_wait + 833
2   libsystem_c.dylib
0x923310a1 pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore
0x95478492 TSWaitOnCondition + 128
4   com.apple.CoreServices.CarbonCore
0x9547868e TSWaitOnConditionTimedRelative + 146
5   com.apple.CoreServices.CarbonCore
0x953c4b9b MPWaitOnQueue + 261
6   AdobeACE
0x0149638d 0x1465000 + 201613
7   AdobeACE
0x01495d85 0x1465000 + 200069
8   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
9   libsystem_c.dylib
0x922a6557 _pthread_start + 344
10 libsystem_c.dylib
0x92290cee thread_start + 34
Thread 7:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab220 _pthread_cond_wait + 833
2   libsystem_c.dylib
0x923310a1 pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore
0x95478492 TSWaitOnCondition + 128
4   com.apple.CoreServices.CarbonCore
0x9547868e TSWaitOnConditionTimedRelative + 146
5   com.apple.CoreServices.CarbonCore
0x953c4b9b MPWaitOnQueue + 261
6   AdobeACE
0x0149638d 0x1465000 + 201613
7   AdobeACE
0x01495d85 0x1465000 + 200069
8   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
9   libsystem_c.dylib
0x922a6557 _pthread_start + 344
10 libsystem_c.dylib
0x92290cee thread_start + 34
Thread 8:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab220 _pthread_cond_wait + 833
2   libsystem_c.dylib
0x923310a1 pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore
0x95478492 TSWaitOnCondition + 128
4   com.apple.CoreServices.CarbonCore
0x9547868e TSWaitOnConditionTimedRelative + 146
5   com.apple.CoreServices.CarbonCore
0x953c4b9b MPWaitOnQueue + 261
6   AdobeACE
0x0149638d 0x1465000 + 201613
7   AdobeACE
0x01495d85 0x1465000 + 200069
8   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
9   libsystem_c.dylib
0x922a6557 _pthread_start + 344
10 libsystem_c.dylib
0x92290cee thread_start + 34
Thread 9:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab220 _pthread_cond_wait + 833
2   libsystem_c.dylib
0x923310a1 pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore
0x95478492 TSWaitOnCondition + 128
4   com.apple.CoreServices.CarbonCore
0x9547868e TSWaitOnConditionTimedRelative + 146
5   com.apple.CoreServices.CarbonCore
0x953c4b9b MPWaitOnQueue + 261
6   AdobeACE
0x0149638d 0x1465000 + 201613
7   AdobeACE
0x01495d85 0x1465000 + 200069
8   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
9   libsystem_c.dylib
0x922a6557 _pthread_start + 344
10 libsystem_c.dylib
0x92290cee thread_start + 34
Thread 10:
0   libsystem_kernel.dylib
0x9967f826 semaphore_timedwait_trap + 10
1   com.apple.CoreServices.CarbonCore
0x9544b810 MPWaitOnSemaphore + 106
2   MultiProcessor Support
0x09a32eff 0x9a03000 + 196351
3   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
4   libsystem_c.dylib
0x922a6557 _pthread_start + 344
5   libsystem_c.dylib
0x92290cee thread_start + 34
Thread 11:
0   libsystem_kernel.dylib
0x9967f826 semaphore_timedwait_trap + 10
1   com.apple.CoreServices.CarbonCore
0x9544b810 MPWaitOnSemaphore + 106
2   MultiProcessor Support
0x09a32eff 0x9a03000 + 196351
3   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
4   libsystem_c.dylib
0x922a6557 _pthread_start + 344
5   libsystem_c.dylib
0x92290cee thread_start + 34
Thread 12:
0   libsystem_kernel.dylib
0x9967f826 semaphore_timedwait_trap + 10
1   com.apple.CoreServices.CarbonCore
0x9544b810 MPWaitOnSemaphore + 106
2   MultiProcessor Support
0x09a32eff 0x9a03000 + 196351
3   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
4   libsystem_c.dylib
0x922a6557 _pthread_start + 344
5   libsystem_c.dylib
0x92290cee thread_start + 34
Thread 13:
0   libsystem_kernel.dylib
0x9967f826 semaphore_timedwait_trap + 10
1   com.apple.CoreServices.CarbonCore
0x9544b810 MPWaitOnSemaphore + 106
2   MultiProcessor Support
0x09a32eff 0x9a03000 + 196351
3   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
4   libsystem_c.dylib
0x922a6557 _pthread_start + 344
5   libsystem_c.dylib
0x92290cee thread_start + 34
Thread 14:
0   libsystem_kernel.dylib
0x9967f826 semaphore_timedwait_trap + 10
1   com.apple.CoreServices.CarbonCore
0x9544b810 MPWaitOnSemaphore + 106
2   MultiProcessor Support
0x09a32eff 0x9a03000 + 196351
3   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
4   libsystem_c.dylib
0x922a6557 _pthread_start + 344
5   libsystem_c.dylib
0x92290cee thread_start + 34
Thread 15:
0   libsystem_kernel.dylib
0x9967f826 semaphore_timedwait_trap + 10
1   com.apple.CoreServices.CarbonCore
0x9544b810 MPWaitOnSemaphore + 106
2   MultiProcessor Support
0x09a32eff 0x9a03000 + 196351
3   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
4   libsystem_c.dylib
0x922a6557 _pthread_start + 344
5   libsystem_c.dylib
0x92290cee thread_start + 34
Thread 16:
0   libsystem_kernel.dylib
0x9967f826 semaphore_timedwait_trap + 10
1   com.apple.CoreServices.CarbonCore
0x9544b810 MPWaitOnSemaphore + 106
2   MultiProcessor Support
0x09a32eff 0x9a03000 + 196351
3   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
4   libsystem_c.dylib
0x922a6557 _pthread_start + 344
5   libsystem_c.dylib
0x92290cee thread_start + 34
Thread 17:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab220 _pthread_cond_wait + 833
2   libsystem_c.dylib
0x923310a1 pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore
0x95478492 TSWaitOnCondition + 128
4   com.apple.CoreServices.CarbonCore
0x9547868e TSWaitOnConditionTimedRelative + 146
5   com.apple.CoreServices.CarbonCore
0x953c4b9b MPWaitOnQueue + 261
6   com.adobe.CameraRaw
0x0e9ea8b8 0xe800000 + 2009272
7   com.adobe.CameraRaw
0x0e9ea1b6 0xe800000 + 2007478
8   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
9   libsystem_c.dylib
0x922a6557 _pthread_start + 344
10 libsystem_c.dylib
0x92290cee thread_start + 34
Thread 18:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab220 _pthread_cond_wait + 833
2   libsystem_c.dylib
0x923310a1 pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore
0x95478492 TSWaitOnCondition + 128
4   com.apple.CoreServices.CarbonCore
0x9547868e TSWaitOnConditionTimedRelative + 146
5   com.apple.CoreServices.CarbonCore
0x953c4b9b MPWaitOnQueue + 261
6   com.adobe.CameraRaw
0x0e9ea8b8 0xe800000 + 2009272
7   com.adobe.CameraRaw
0x0e9ea1b6 0xe800000 + 2007478
8   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
9   libsystem_c.dylib
0x922a6557 _pthread_start + 344
10 libsystem_c.dylib
0x92290cee thread_start + 34
Thread 19:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab220 _pthread_cond_wait + 833
2   libsystem_c.dylib
0x923310a1 pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore
0x95478492 TSWaitOnCondition + 128
4   com.apple.CoreServices.CarbonCore
0x9547868e TSWaitOnConditionTimedRelative + 146
5   com.apple.CoreServices.CarbonCore
0x953c4b9b MPWaitOnQueue + 261
6   com.adobe.CameraRaw
0x0e9ea8b8 0xe800000 + 2009272
7   com.adobe.CameraRaw
0x0e9ea1b6 0xe800000 + 2007478
8   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
9   libsystem_c.dylib
0x922a6557 _pthread_start + 344
10 libsystem_c.dylib
0x92290cee thread_start + 34
Thread 20:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab220 _pthread_cond_wait + 833
2   libsystem_c.dylib
0x923310a1 pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore
0x95478492 TSWaitOnCondition + 128
4   com.apple.CoreServices.CarbonCore
0x9547868e TSWaitOnConditionTimedRelative + 146
5   com.apple.CoreServices.CarbonCore
0x953c4b9b MPWaitOnQueue + 261
6   com.adobe.CameraRaw
0x0e9ea8b8 0xe800000 + 2009272
7   com.adobe.CameraRaw
0x0e9ea1b6 0xe800000 + 2007478
8   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
9   libsystem_c.dylib
0x922a6557 _pthread_start + 344
10 libsystem_c.dylib
0x92290cee thread_start + 34
Thread 21:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab220 _pthread_cond_wait + 833
2   libsystem_c.dylib
0x923310a1 pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore
0x95478492 TSWaitOnCondition + 128
4   com.apple.CoreServices.CarbonCore
0x9547868e TSWaitOnConditionTimedRelative + 146
5   com.apple.CoreServices.CarbonCore
0x953c4b9b MPWaitOnQueue + 261
6   com.adobe.CameraRaw
0x0e9ea8b8 0xe800000 + 2009272
7   com.adobe.CameraRaw
0x0e9ea1b6 0xe800000 + 2007478
8   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
9   libsystem_c.dylib
0x922a6557 _pthread_start + 344
10 libsystem_c.dylib
0x92290cee thread_start + 34
Thread 22:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab220 _pthread_cond_wait + 833
2   libsystem_c.dylib
0x923310a1 pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore
0x95478492 TSWaitOnCondition + 128
4   com.apple.CoreServices.CarbonCore
0x9547868e TSWaitOnConditionTimedRelative + 146
5   com.apple.CoreServices.CarbonCore
0x953c4b9b MPWaitOnQueue + 261
6   com.adobe.CameraRaw
0x0e9ea8b8 0xe800000 + 2009272
7   com.adobe.CameraRaw
0x0e9ea1b6 0xe800000 + 2007478
8   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
9   libsystem_c.dylib
0x922a6557 _pthread_start + 344
10 libsystem_c.dylib
0x92290cee thread_start + 34
Thread 23:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab220 _pthread_cond_wait + 833
2   libsystem_c.dylib
0x923310a1 pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore
0x95478492 TSWaitOnCondition + 128
4   com.apple.CoreServices.CarbonCore
0x9547868e TSWaitOnConditionTimedRelative + 146
5   com.apple.CoreServices.CarbonCore
0x953c4b9b MPWaitOnQueue + 261
6   com.adobe.CameraRaw
0x0e9ea8b8 0xe800000 + 2009272
7   com.adobe.CameraRaw
0x0e9ea1b6 0xe800000 + 2007478
8   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
9   libsystem_c.dylib
0x922a6557 _pthread_start + 344
10 libsystem_c.dylib
0x92290cee thread_start + 34
Thread 24:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab289 _pthread_cond_wait + 938
2   libsystem_c.dylib
0x92338afc pthread_cond_wait + 48
3   com.adobe.CameraRaw
0x0e845aea 0xe800000 + 285418
4   com.adobe.CameraRaw
0x0eb2d2f4 EntryFM + 836980
5   com.adobe.CameraRaw
0x0e9024a6 0xe800000 + 1057958
6   libsystem_c.dylib
0x922a6557 _pthread_start + 344
7   libsystem_c.dylib
0x92290cee thread_start + 34
Thread 25:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab289 _pthread_cond_wait + 938
2   libsystem_c.dylib
0x92338afc pthread_cond_wait + 48
3   com.adobe.CameraRaw
0x0e845aea 0xe800000 + 285418
4   com.adobe.CameraRaw
0x0ebbd118 EntryFM + 1426328
5   com.adobe.CameraRaw
0x0e9024a6 0xe800000 + 1057958
6   libsystem_c.dylib
0x922a6557 _pthread_start + 344
7   libsystem_c.dylib
0x92290cee thread_start + 34
Thread 26:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab289 _pthread_cond_wait + 938
2   libsystem_c.dylib
0x92338b30 pthread_cond_timedwait + 47
3   com.adobe.bridge3
0x005f9ff5 vio_timeout + 121907
4   com.adobe.bridge3
0x005fa683 vio_timeout + 123585
5   com.adobe.bridge3
0x005fa6e2 vio_timeout + 123680
6   com.adobe.bridge3
0x0048ecd4 Mondo::CThread::EntryProc() + 18
7   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
8   libsystem_c.dylib
0x922a6557 _pthread_start + 344
9   libsystem_c.dylib
0x92290cee thread_start + 34
Thread 27:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab289 _pthread_cond_wait + 938
2   libsystem_c.dylib
0x92338b30 pthread_cond_timedwait + 47
3   com.adobe.bridge3
0x005f9ff5 vio_timeout + 121907
4   com.adobe.bridge3
0x005fa683 vio_timeout + 123585
5   com.adobe.bridge3
0x005fa6e2 vio_timeout + 123680
6   com.adobe.bridge3
0x0048ecd4 Mondo::CThread::EntryProc() + 18
7   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
8   libsystem_c.dylib
0x922a6557 _pthread_start + 344
9   libsystem_c.dylib
0x92290cee thread_start + 34
Thread 28:
0   libsystem_kernel.dylib
0x9967f8e6 mach_wait_until + 10
1   libsystem_c.dylib
0x92337c1c nanosleep + 375
2   com.adobe.bridge3
0x00388b0d VCUI_Terminate + 1517031
3   com.adobe.bridge3
0x00388b6d VCUI_Terminate + 1517127
4   com.adobe.bridge3
0x00367916 VCUI_Terminate + 1381360
5   com.adobe.bridge3
0x00388f93 VCUI_Terminate + 1518189
6   libsystem_c.dylib
0x922a6557 _pthread_start + 344
7   libsystem_c.dylib
0x92290cee thread_start + 34
Thread 29:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab289 _pthread_cond_wait + 938
2   libsystem_c.dylib
0x92338b30 pthread_cond_timedwait + 47
3   com.adobe.bridge3
0x005f9ff5 vio_timeout + 121907
4   com.adobe.bridge3
0x0063a3c6 vio_timeout + 385028
5   com.adobe.bridge3
0x0048ecd4 Mondo::CThread::EntryProc() + 18
6   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
7   libsystem_c.dylib
0x922a6557 _pthread_start + 344
8   libsystem_c.dylib
0x92290cee thread_start + 34
Thread 30:
0   libsystem_kernel.dylib
0x996818e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x922ab289 _pthread_cond_wait + 938
2   libsystem_c.dylib
0x92338b30 pthread_cond_timedwait + 47
3   com.adobe.bridge3
0x005f9ff5 vio_timeout + 121907
4   com.adobe.bridge3
0x00ac5f5e st_tz_names_entry::st_tz_names_entry() + 1986
5   com.adobe.bridge3
0x005dd9d4 vio_timeout + 5650
6   com.adobe.bridge3
0x0048ecd4 Mondo::CThread::EntryProc() + 18
7   com.apple.CoreServices.CarbonCore
0x9544ba7b PrivateMPEntryPoint + 68
8   libsystem_c.dylib
0x922a6557 _pthread_start + 344
9   libsystem_c.dylib
0x92290cee thread_start + 34
Thread 31:
0   libsystem_kernel.dylib
0x996820ee __workq_kernreturn + 10
1   libsystem_c.dylib
0x922a904c _pthread_workq_return + 45
2   libsystem_c.dylib
0x922a8e19 _pthread_wqthread + 448
3   libsystem_c.dylib
0x92290cca start_wqthread + 30
Thread 32:
0   libsystem_kernel.dylib
0x996820ee __workq_kernreturn + 10
1   libsystem_c.dylib
0x922a904c _pthread_workq_return + 45
2   libsystem_c.dylib
0x922a8e19 _pthread_wqthread + 448
3   libsystem_c.dylib
0x92290cca start_wqthread + 30
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x1f01367e ecx: 0x00000000 edx: 0x00002060
edi: 0x00000000 esi: 0x1e140616 ebp: 0xbfffc308 esp: 0xbfffc290
   ss: 0x00000023 efl: 0x00010246 eip: 0x1f013730   cs: 0x0000001b
   ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f
cr2: 0x00000000
Logical CPU: 6
Binary Images:
0x1000 -   0xcd7ff7 +com.adobe.bridge3 (3.0.0.464 - 3.0.0.464) <1B6A56FB-E649-4A04-B272-80FEA8737FEB> /Applications/Adobe Bridge CS4/Adobe Bridge CS4.app/Contents/MacOS/Adobe Bridge CS4
0x13bf000 - 0x13fffef +AdobeARE (1) /Applications/Adobe Bridge CS4/Adobe Bridge CS4.app/Contents/Frameworks/AdobeARE.framework/Versions/A/AdobeARE
0x1409000 - 0x142dff6 +AdobeAXE8SharedExpat (0) /Applications/Adobe Bridge CS4/Adobe Bridge CS4.app/Contents/Frameworks/AdobeAXE8SharedExpat.framework/Versions/A/AdobeAXE8SharedExpa t
0x1440000 - 0x145afff +AdobeBIB (1) /Applications/Adobe Bridge CS4/Adobe Bridge CS4.app/Contents/Frameworks/AdobeBIB.framework/Versions/A/AdobeBIB
0x1465000 - 0x1572fff +AdobeACE (1) /Applications/Adobe Bridge CS4/Adobe Bridge CS4.app/Contents/Frameworks/AdobeACE.framework/Versions/A/AdobeACE
0x1590000 - 0x182cfef +AdobeCoolType (1) /Applications/Adobe Bridge CS4/Adobe Bridge CS4.app/Contents/Frameworks/AdobeCoolType.

Still crashes the same way.
Running a bit out of options I'm afraid.
To be absolutely sure, you also did the 2.1 update for the Output Module:
http://www.adobe.com/support/downloads/detail.jsp?ftpID=4229
Not sure the link works, sometimes they are country specific but otherwise check the downloads at Adobe.com
Did you try it in a new user account just for testing. Sometimes check and repair permissions using Apple Disk Utility (or 3th party like Cocktail) will also help.
And finally I should point you to the fact that due to a new upgrade policy from Adobe you have until 31 december this year to profit from the upgrade price for PS CS6, after the 1st of january 2013 you will have to pay the full license price for CS6.

How do i save FSG xml report output to External Drive.

We are implementing XML publisher to replace our ADI. How i save xml publisher report output to network drive also need to change report name dynamically.
The answer from oracle is
:There is no built-in functionality to do what is requested however,
the output file exists at the O/S level and a printer DRIVER can be created and in the "Arguments" field, a copy command can be entered instead of the print command"
how do i implement this. help please
Thx

Make sure the drive is formatted Mac OS Extended (Journaled)
Do you want to merge these libraries into one? If so, then you'll need the paid version ($20) of iPhoto Library Manager
It's the only way to merge Libraries while preserving all metadata, versions and so on.
Otherwise, simply rename one of the Libraries (so they don't overwite each other) and Copy the iPhoto Library from the Pictures Folder to the External Disk. in each case.
To choose which library to open: holf down the option (or alt) key while launching iPhoto. From the resulting menu select 'Choose Library' and navigate to the new location.
Regards
TD

Berkeley DB XML crash with multiple readers (dbxml-2.5.16 and db-4.8.26)

I am using Berkeley DB XML (v. 2.5.16 and the bundled underlying Berkeley DB 4.8.26, which I suppose is now fairly old) to manage an XML database which is read by a large number (order 100) of independent worker processes communicating via MPI. These processes only read from the database; a single master process performs writes.
Everything works as expected with one or two worker processes. But with three or more, I am experiencing database panics with the error
pthread lock failed: Invalid argument
PANIC: Invalid argument
From searching with Google I can see that issues arising from incorrectly setting up the environment to support concurrency are are fairly common. But I have not been able to find a match for this problem, and as far as I can make out from the documentation I am using the correct combination of flags; I use DB_REGISTER and DB_RECOVER to handle the fact that multiple processes join the environment independently. Each process uses on a single environment handle, and joins using
DB_ENV* env;
db_env_create(&env, 0);
u_int32_t env_flags = DB_INIT_LOG | DB_INIT_MPOOL | DB_REGISTER | DB_RECOVER | DB_INIT_TXN | DB_CREATE;
env->open(env, path to environment, env_flags, 0);
Although the environment requests DB_INIT_TXN, I am not currently using transactions. There is an intention to implement this later, but my understanding was that concurrent reads would function correctly without the full transaction infrastructure.
All workers seem to join the environment correctly, but then fail when an attempt is made to read from the database. They will all try to access the same XML document in the same container (because it gives them instructions about what work to perform). However, the worker processes open each container setting the read-only flag:
DbXml::XmlContainerConfig models_config;
models_config.setReadOnly(true);
DbXml::XmlContainer models = this->mgr->openContainer(path to container, models_config);
Following the database panic, the stack trace is
[lcd-ds283:27730] [ 0] 2   libsystem_platform.dylib            0x00007fff8eed35aa _sigtramp + 26
[lcd-ds283:27730] [ 1] 3   ???                                 0x0000000000000000 0x0 + 0
[lcd-ds283:27730] [ 2] 4   libsystem_c.dylib                   0x00007fff87890bba abort + 125
[lcd-ds283:27730] [ 3] 5   libc++abi.dylib                     0x00007fff83aff141 __cxa_bad_cast + 0
[lcd-ds283:27730] [ 4] 6   libc++abi.dylib                     0x00007fff83b24aa4 _ZL25default_terminate_handlerv + 240
[lcd-ds283:27730] [ 5] 7   libobjc.A.dylib                     0x00007fff89ac0322 _ZL15_objc_terminatev + 124
[lcd-ds283:27730] [ 6] 8   libc++abi.dylib                     0x00007fff83b223e1 _ZSt11__terminatePFvvE + 8
[lcd-ds283:27730] [ 7] 9   libc++abi.dylib                     0x00007fff83b21e6b _ZN10__cxxabiv1L22exception_cleanup_funcE19_Unwind_Reason_CodeP17_Unwind_Exception + 0
[lcd-ds283:27730] [ 8] 10 libdbxml-2.5.dylib                  0x000000010f30e4de _ZN5DbXml18DictionaryDatabaseC2EP8__db_envPNS_11TransactionERKNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEERKNS_15ContainerConfigEb + 1038
[lcd-ds283:27730] [ 9] 11 libdbxml-2.5.dylib                  0x000000010f2f348c _ZN5DbXml9Container12openInternalEPNS_11TransactionERKNS_15ContainerConfigEb + 1068
[lcd-ds283:27730] [10] 12 libdbxml-2.5.dylib                  0x000000010f2f2dec _ZN5DbXml9ContainerC2ERNS_7ManagerERKNSt3__112basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEEPNS_11TransactionERKNS_15ContainerConfigEb + 492
[lcd-ds283:27730] [11] 13 libdbxml-2.5.dylib                  0x000000010f32a0af _ZN5DbXml7Manager14ContainerStore13findContainerERS0_RKNSt3__112basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEEPNS_11TransactionERKNS_15ContainerConfigEb + 175
[lcd-ds283:27730] [12] 14 libdbxml-2.5.dylib                  0x000000010f329f75 _ZN5DbXml7Manager13openContainerERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEPNS_11TransactionERKNS_15ContainerConfigEb + 101
[lcd-ds283:27730] [13] 15 libdbxml-2.5.dylib                  0x000000010f34cd46 _ZN5DbXml10XmlManager13openContainerERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEERKNS_18XmlContainerConfigE + 102
Can I ask if it's clear to anyone what I am doing wrong?

Is it possible that the root problem to this is in the MPI code or usage? Because if the writer process crashes while holding an active transaction or open database handles, it could leave the environment in an inconsistent state that would result in the readers throwing a PANIC error when they notice the inconsistent environment.
Thanks for looking into this.
It looks like there was a small typo in the code I quoted, and I think it was this which caused the segmentation fault or memory corruption. Although I checked a few times that the code snippet produced expected results before posting it, I must have been unlucky that it just happened not to cause a segfault on those attempts.
This is a corrected version:
#include <iostream>
#include <vector>
#include "dbxml/db.h"
#include "dbxml/dbxml/DbXml.hpp"
#include "boost/mpi.hpp"
static std::string envname = std::string("test");
static std::string pkgname = std::string("packages.dbxml");
static std::string intname = std::string("integrations.dbxml");
int main(int argc, char *argv[])
    boost::mpi::environment mpi_env;
    boost::mpi::communicator mpi_world;
    if(mpi_world.rank() == 0)
        std::cerr << "-- Writer creating environment" << std::endl;
        DB_ENV *env;
        int dberr = ::db_env_create(&env, 0);
        std::cerr << "**   creation response = " << dberr << std::endl;
        if(dberr > 0) std::cerr << "**   " << ::db_strerror(dberr) << std::endl;
        std::cerr << "-- Writer opening environment" << std::endl;
        u_int32_t env_flags = DB_INIT_LOCK | DB_INIT_LOG | DB_INIT_MPOOL | DB_REGISTER | DB_RECOVER | DB_INIT_TXN | DB_CREATE;
        dberr = env->open(env, envname.c_str(), env_flags, 0);
        std::cerr << "**   opening response = " << dberr << std::endl;
        if(dberr > 0) std::cerr << "**   " << ::db_strerror(dberr) << std::endl;
        // set up XmlManager object
        DbXml::XmlManager *mgr = new DbXml::XmlManager(env, DbXml::DBXML_ADOPT_DBENV | DbXml::DBXML_ALLOW_EXTERNAL_ACCESS);
        // create containers - these will be used by the workers
        DbXml::XmlContainerConfig pkg_config;
        DbXml::XmlContainerConfig int_config;
        pkg_config.setTransactional(true);
        int_config.setTransactional(true);
        std::cerr << "-- Writer creating containers" << std::endl;
        DbXml::XmlContainer packages       = mgr->createContainer(pkgname.c_str(), pkg_config);
        DbXml::XmlContainer integrations   = mgr->createContainer(intname.c_str(), int_config);
        std::cerr << "-- Writer instructing workers" << std::endl;
        std::vector<boost::mpi::request> reqs(mpi_world.size() - 1);
        for(unsigned int                 i = 1; i < mpi_world.size(); i++)
            reqs[i - 1] = mpi_world.isend(i, 0); // instruct workers to open the environment
        // wait for all messages to be received
        boost::mpi::wait_all(reqs.begin(), reqs.end());
        std::cerr << "-- Writer waiting for termination responses" << std::endl;
        // wait for workers to advise successful termination
        unsigned int outstanding_workers = mpi_world.size() - 1;
        while(outstanding_workers > 0)
            boost::mpi::status stat = mpi_world.probe();
            switch(stat.tag())
                case 1:
                    mpi_world.recv(stat.source(), 1);
                    outstanding_workers--;
                    break;
        delete mgr; // exit, closing database and environment
    else
        mpi_world.recv(0, 0);
        std::cerr << "++ Reader " << mpi_world.rank() << " beginning work" << std::endl;
        DB_ENV *env;
        ::db_env_create(&env, 0);
        u_int32_t env_flags = DB_INIT_LOCK | DB_INIT_LOG | DB_INIT_MPOOL | DB_REGISTER | DB_RECOVER | DB_INIT_TXN | DB_CREATE;
        env->open(env, envname.c_str(), env_flags, 0);
        // set up XmlManager object
        DbXml::XmlManager *mgr = new DbXml::XmlManager(env, DbXml::DBXML_ADOPT_DBENV | DbXml::DBXML_ALLOW_EXTERNAL_ACCESS);
        // open containers which were set up by the master
        DbXml::XmlContainerConfig pkg_config;
        DbXml::XmlContainerConfig int_config;
        pkg_config.setTransactional(true);
        pkg_config.setReadOnly(true);
        int_config.setTransactional(true);
        int_config.setReadOnly(true);
        DbXml::XmlContainer packages     = mgr->openContainer(pkgname.c_str(), pkg_config);
        DbXml::XmlContainer integrations = mgr->openContainer(intname.c_str(), int_config);
        mpi_world.isend(0, 1);
        delete mgr; // exit, closing database and environment
    return (EXIT_SUCCESS);
This repeatably causes the crash on OS X Mavericks 10.9.1. Also, I have checked that it repeatably causes the crash on a virtualized OS X Mountain Lion 10.8.5. But I do not see any crashes on a virtualized Ubuntu 13.10. My full code likewise works as expected with a large number of readers under the virtualized Ubuntu. I am compiling with clang and libc++ on OS X, and gcc 4.8.1 and libstdc++ on Ubuntu, but using openmpi in both cases. Edit: I have also compiled with clang and libc++ on Ubuntu, and it works equally well.
Because the virtualized OS X experiences the crash, I hope the fact that it works on Ubuntu is not just an artefact of virtualization. (Unfortunately I don't currently have a physical Linux machine with which to check.) In that case the implication would seem to be that it's an OS X-specific problem. 2nd edit (14 Feb 2014): I have now managed to test on a physical Linux cluster, and it appears to work as expected. Therefore it does appear to be an OS X-specific issue.
In either OS X 10.8 or 10.9, the crash produces this result:
-- Writer creating environment
**   creation response = 0
-- Writer opening environment
**   opening response = 0
-- Writer creating containers
++ Reader 7 beginning work
-- Writer instructing workers
-- Writer waiting for termination responses
++ Reader 1 beginning work
++ Reader 2 beginning work
++ Reader 3 beginning work
++ Reader 4 beginning work
++ Reader 5 beginning work
++ Reader 6 beginning work
pthread lock failed: Invalid argument
PANIC: Invalid argument
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
libc++abi.dylib: terminate called throwing an exception
[mountainlion-test-rig:00319] *** Process received signal ***
[mountainlion-test-rig:00319] Signal: Abort trap: 6 (6)
[mountainlion-test-rig:00319] Signal code: (0)
David
Message was edited by: ds283

MBP doesn't save files, then crashes - Illustrator

Hi...I'm in need of some direction on what to do here. My Illustrator CS2 program on my first generation MBP decided to crash and not register any of the saves I made before the crash. I had been hitting "Save" in Illustrator for over 2 hours, and when the program "unexpectedly quit" I went to reopen Illustrator and the file only to find a very old version, not a version saved 2 minutes ago.
It's worse this morning, Illustrator CS2 is crashing every couple of minutes, and the "saved" file is a few "saves" back, if that makes sense. I just can't get Illustrator to save my file to disk, or to memory stick, or the anything else. It's like my saves don't register, and almost anything I do in Illustrator crashes the program.
Is this a hard-drive problem? A RAM problem? I have sneaking suspicions something is up with my logic board..anyways, it's the only other problem with the macbook pro (see http://www.mac-forums.com/forums/sho...101#post487101)
any help, advice, or direction would be appreciated.
vikki

Illustrator CS3 puts files in the following places…
~/Library/Application Support/Adobe/Adobe Illustrator CS3
~/Library/Preferences/Adobe Save For Web AI 12.0 Prefs
~/Library/Preferences/Adobe Illustrator CS3 Settings
What you can do is you move all/some of these files to you desktop, reset your AI settings and see if your problem goes. By moving them to you desktop you leave yourself the opportunity to put them back if it doesn't fix things by having AI make new ones.

FrameMaker 12 Save as XML crash

Similar Messages

Maybe you are looking for