[Enigmail] IPC library usage

[Patrick Brunschwig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Damiano Albani wrote:
> Hello,
> 
> On Jan 25, 2008 11:58 AM, Patrick Brunschwig
> <patrick at mozilla-enigmail.org <mailto:patrick at mozilla-enigmail.org>> wrote:
> 
>     - From where did you actually get your binary IPC library and with what
>     Mozilla product do you try to use it? You might simply have run into
>     compatibility issues between the various Mozilla builds.
> 
> 
> I'm using the IPC library which is "embedded" in the "enigmime.dll"
> file, which I took from the "enigmail-0.95.6-tb+sm.xpi" archive.
> In combination with the official Win32 Thunderbird 2.0.0.9
> <http://2.0.0.9> version.
> 
>     For logging, just use a command line and define these to env. vars:
> 
>     set NSPR_LOG_MODULES=nsPipeTransport:5
>     set NSPR_LOG_FILE=C:\TEMP\nspr-debug.log
> 
> 
> Did that. Here's the (minimalist) output :
> 
> 0[2745f8]: nsPipeTransport:: <<<<<<<<< CTOR(21e9a00): myThread=278510
> 0[2745f8]: nsPipeTransport::Init: executable=c:\Dummy.exe [0]

I have tried to see if my example works on Windows, and it does work.
Did you actually provide ipc with "c:\Dummy.exe" or "c:\\Dummy.exe" ?
The double backslash is mandatory for JavaScript to identify a native
"\". If that doesn't help then you could maybe try to replace
"C:\dummy.exe with C:\\windows\\system32\\cmd.exe /c dir C:\\"

- -Patrick



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.8 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEVAwUBR6cCEHcOpHodsOiwAQKN3gf/UM6CaNRZimmD8mfVE35nnkQiS50MRp0V
r7yIhgXcGBO54pLWqrUeJQkHcyBIngLQhDG7nuFX7beO+KD4i18ho5Pj4qfaxvkP
UQLfKeEfFCUNeF0l2O84gpwbiGTKFyMwmvVL5HiG60oH6TQoInZ2+BeLQolOE5v7
mfhJ0UwJsAauv8FSNRKhBQjl3YYG+SQ4cqN+YNXfurOUoVP3GhC0AnfDbEJwawl9
DHj0rexJrqwjs+dnnO6DC+WTYP/KatPSV2ryncLzPffbX/Y1U5QlQUYJwEEPNC2D
zfzvYzkoCqngk9bmVl43EVrelBn+CiBnfNfjBury9DHWvBtm5wgc3Q==
=LTI1
-----END PGP SIGNATURE-----