external extension failed on win32

[Simon Mieth]

An external import extension fails. The external tool works on the Windows shell and inkscape can import the generated file from the tool. Using the tool as import extensions fails with following error message:

Microsoft Visual C++ Runtime Library
Runtime Error!
Inkscape internal error

The extension works with Inkscape 0.45.1 and earlier.

[Ted Gould (ted)]

If possible could you please try this with Inkscape trunk. There are a couple of Win32 patchs for paths that have been recently applied there. It might fix your problems also.

[Simon Mieth (simon-mieth)]

I tried it with the 17888 revision from SVN, but it fails too on this version. Inkscape shows up a Runtime Error Message Box. There is no backtrace in gdb
only the message "Program exited with code 03". The extension works with 0.45.1 correct (a Shell Window is visible). The shell window never open in Inkscape 0.46-dev.
So It looks like the external extension is never started.

[Alvin Penner (apenner)]

if you have Inkscape crashes in Windows, then check out the website :
    http://kaioa.com/node/42
if you run Inkscape from a DOS prompt using a command like "python InkCL.py", then you can often trap DOS exit messages that you otherwise would not see.

[Simon Mieth (simon-mieth)]

Ok, tried it with this tool and get more info for this problem:

I have seen two different problems:

1.) If I select the extension file type and select a file in the "Open" file dialog, the parameter UI for the extension (which is defined in the extension INX file) is not shown with the following error message "Failed to load the requested file C:\02.dxf".

2.) If Inkscape auto-detected the file type self and select the only the file the correct parameter UI is shown and the import fails with the following error:

return code: 3
terminate called after throwing an instance of 'Glib::SpawnError'

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix

I'm not sure if it the right place here, but the extensions could be found here: http://sf.net/projects/kabeja

[Ulferikson (ulferikson)]

> 1.) If I select the extension file type and select a file in the "Open" file dialog

Sounds like Bug #199357

> 2.) If Inkscape auto-detected the file type self and select the only the file

Sounds like Bug #187290 (but then maybe for java instead of python?)

[Simon Mieth (simon-mieth)]

>> 1.) If I select the extension file type and select a file in the "Open" file dialog

>Sounds like Bug #199357

Yes, sounds like the same.

>> 2.) If Inkscape auto-detected the file type self and select the only the file

>Sounds like Bug #187290 (but then maybe for java instead of python?)

Sounds like the same here, I have tried the patch but same result. The problem is that a shell window for the executable is never visible. The extension can be build as
java version, .NET or static linked gcj compiled binary and no version works. The PATH is setup in Windows (XP SP2) and all versions could be used in a Windows shell.
So I'm not sure if its the same, but it looks like a environment problem too.
Has someone an extension working which runs in a shell window with Inkscape 0.46?

[Alvin Penner (apenner)]

running win32 build 0803141639.7z
choose Effects | Color | Brighter and Inkscape crashes

C:\Program Files\Inkscape\python>python \python25\app\inkcl.py
return code: 3
** Message: Found local interpreter, 'C:\Program Files\Inkscape\python\pythonw.e
xe', Size: 24576
terminate called after throwing an instance of 'Glib::SpawnError'

It appears that everything that is python-related is broken

[Alvin Penner (apenner)]

here is the backtrace:

C:\Program Files>cd inkscape

C:\Program Files\Inkscape>gdb inkscape
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-mingw32"...
(no debugging symbols found)
(gdb) symbol-file inkscape.dbg
Reading symbols from C:\Program Files\Inkscape/inkscape.dbg...done.
(gdb) run
Starting program: C:\Program Files\Inkscape/inkscape.exe
Loaded symbols for C:\WINDOWS\system32\ntdll.dll
Loaded symbols for C:\WINDOWS\system32\kernel32.dll
Loaded symbols for C:\Program Files\Inkscape\libatkmm-1.6-1.dll
Loaded symbols for C:\Program Files\Inkscape\libatk-1.0-0.dll
Loaded symbols for C:\Program Files\Inkscape\libglib-2.0-0.dll
Loaded symbols for C:\Program Files\Inkscape\intl.dll
Loaded symbols for C:\WINDOWS\system32\msvcrt.dll
Loaded symbols for C:\WINDOWS\system32\advapi32.dll
Loaded symbols for C:\WINDOWS\system32\rpcrt4.dll
Loaded symbols for C:\WINDOWS\system32\ole32.dll
Loaded symbols for C:\WINDOWS\system32\gdi32.dll
Loaded symbols for C:\WINDOWS\system32\user32.dll
Loaded symbols for C:\WINDOWS\system32\shell32.dll
Loaded symbols for C:\WINDOWS\system32\shlwapi.dll
Loaded symbols for C:\WINDOWS\system32\ws2_32.dll
Loaded symbols for C:\WINDOWS\system32\ws2help.dll
Loaded symbols for C:\Program Files\Inkscape\libgobject-2.0-0.dll
Loaded symbols for C:\Program Files\Inkscape\libglibmm-2.4-1.dll
Loaded symbols for C:\Program Files\Inkscape\libgmodule-2.0-0.dll
Loaded symbols for C:\Program Files\Inkscape\libsigc-2.0-0.dll
Loaded symbols for C:\Program Files\Inkscape\libcairo-2.dll
Loaded symbols for C:\Program Files\Inkscape\libfontconfig-1.dll
Loaded symbols for C:\Program Files\Inkscape\freetype6.dll
Loaded symbols for C:\Program Files\Inkscape\libexpat.dll
Loaded symbols for C:\Program Files\Inkscape\libpng13.dll
Loaded symbols for C:\Program Files\Inkscape\zlib1.dll
Loaded symbols for C:\WINDOWS\system32\msimg32.dll
Loaded symbols for C:\Program Files\Inkscape\libcairomm-1.0-1.dll
Loaded symbols for C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
Loaded symbols for C:\Program Files\Inkscape\libgdk_pixbuf-2.0-0.dll
Loaded symbols for C:\Program Files\Inkscape\jpeg62.dll
Loaded symbols for C:\Program Files\Inkscape\libtiff3.dll
Loaded symbols for C:\Program Files\Inkscape\libpango-1.0-0.dll
Loaded symbols for C:\Program Files\Inkscape\libpangocairo-1.0-0.dll
Loaded symbols for C:\Program Files\Inkscape\libpangowin32-1.0-0.dll
Loaded symbols for C:\WINDOWS\system32\imm32.dll
Loaded symbols for C:\Program Files\Inkscape\libgdkmm-2.4-1.dll
Loaded symbols for C:\Program Files\Inkscape\libgtk-win32-2.0-0.dll
Loaded symbols for C:\WINDOWS\WinSxS\X86_Microsoft.Windows.Common-Controls_6595b
64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\comctl32.dll
Loaded symbols for C:\WINDOWS\system32\comdlg32.dll
Loaded symbols for C:\WINDOWS\system32\winspool.drv
Loaded symbols for C:\Program Files\Inkscape\libpangomm-1.4-1.dll
Loaded symb...

[Alvin Penner (apenner)]

Hello Simon,
    This is somewhat off the topic, but I have a question concerning the behaviour of the kabeja conversion procedure. I have downloaded the file kabeja-inkscape-extension-0.4.zip from your website and I am running it offline directly from a DOS prompt. When I take a single dxf entity like a SPLINE curve and convert it to svg using the kabeja program, then I seem to be getting an svg file that has a multi-segmented line with many individual vertices in it instead of a single spline curve. Is it possible to run kabeja differently, in such a way that one dxf SPLINE will get converted to one svg path element like a "curveto" element (M ... C ... C ... C) or possibly an "elliptical arc" element (M ... A ... A ... A) rather than many "lineto" elements of the type M ... L ... L ... L. The reason is that the "curveto" path element yields a more compact file.
   Anyways, my question is, is this an option that is available when running kabeja?