On Sat, 29 Sep 2012, Frederic Koehler wrote:
> This is on a 64-bit machine. Opening the help window works fine the
> first time [and
> their are no valgrind messages], but after closing it and opening it
> again the program
> segfaults, and there are a lot of valgrind messages about using freed
> memory. If you
> don't close the help window, it works fine and sends the help window
> back to the top.
> I'd expect the same issue on a 32-bit machine, but if it isn't there
> then we could
> investigate further.
dtcreate has so many problems - it is written in a completely
pre-ANSI C. For me it immediately segfaults on:
#0 0x000000000040e318 in create_applicationShell1 (_UxUxParent=0x0)
at CreateActionAppShell.c:1682
1682 UxParent = _UxUxParent;
#0 0x000000000040e318 in create_applicationShell1 (_UxUxParent=0x0)
at CreateActionAppShell.c:1682
#1 0x00000000004085e8 in main (argc=1, argv=0x7fffffffcc88) at main.c:1336
(gdb) print UxParent
No symbol "UxParent" in current context.
(gdb) print _UxUxParent
$1 = 0x0
//Marcin
------------------------------------------------------------------------------
How fast is your code?
3 out of 4 devs don\\\'t know how their code performs in production.
Find out how slow your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219672;13503038;z?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
