Bug 46224 - Interprocess communication via CLI nonfunctional
Summary: Interprocess communication via CLI nonfunctional
Status: RESOLVED DUPLICATE of bug 46832
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: x86-64 (AMD64) Windows (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-17 04:31 UTC by bugzilla
Modified: 2013-02-20 07:43 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugzilla 2012-02-17 04:31:25 UTC
We make a program that communicates with LibreOffice using CLI, which works fine on 3.4.5 and earlier. 

Our program uses .NET Framework 2.0.


Using:

Client: LibreOffice 3.5.0rc3 
Build-ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735

with:
cli_basetypes 1.0.19.0
cli_cppuhelper 1.0.22.0
cli_oootypes 1.0.8.0
cli_ure 1.0.22.0
cli_uretypes 1.0.8.0


Calling uno.util.Bootstrap.bootstrap(); 
in Debug results in:
LoaderLock

Calling the same in release results in:
R6034
An application has made an attempt to load the C runtime library
incorrectly.
Comment 1 PAlex 2012-02-29 00:53:08 UTC
Same way (x86 only tested), same version, same result.

In our C# application.
XComponentContext localContext = uno.util.Bootstrap.bootstrap();

System.Runtime.InteropServices.SEHException
Message : Un composant externe a levé une exception.
Source : cli_cppuhelper
StackTrace :    
à cppu.bootstrap(Reference<com::sun::star::uno::XComponentContext>* )
   à uno.util.Bootstrap.bootstrap()
   à LO.Start() {...}
TargetSite :
{com.sun.star.uno.Reference<com::sun::star::uno::XComponentContext>* cppu.bootstrap(com.sun.star.uno.Reference<com::sun::star::uno::XComponentContext>*)}
Comment 2 Marten Feldtmann 2012-03-07 00:23:32 UTC
See also here:

https://bugs.freedesktop.org/show_bug.cgi?id=46832
Comment 3 Thomas Arnhold 2013-02-20 07:42:34 UTC

*** This bug has been marked as a duplicate of bug 46832 ***