This is not very repeatable - sometimes the stdout/stderr goes away, other times it hangs around. Pops open (albeit slowly) the Inkscape GUI, quit the GUI and drrun shows both CPU time and Memory statistics. Open another command prompt window and in that inkscape has stdout (or stderr) again: So drrun.exe has redirected stdout (or stderr), apparently permanently, for the Command Prompt window. (opens a GUI, but without console messages) (emits CR or other blank line, does not open a GUI) (shows version number and exits, without opening a GUI)Ĭ:\Temp\DynamoRIO-Windows-3.2.0-3\bin32\drrun.exe inkscape.exe -V The debugging Dr.Memory page suggested running drrun by itself, but doesn't give any details. Ran a control on a simple command line windows program, and Dr.Memory had no problem with it. Run on the inkscape.exe built with symbols not stripped and with the two static libraries \drmemory.exe -debug -call_stack_frames 100 -verbose 2 inkscape.exe -V Since no ldmp file was produced, I am sending the log file for Please provide any additional information below.
What about when running with the options "-leaks_only Does the problem go away when running in light mode (pass "-light" to Dr. Memory one of the inkscape binary distributions will probably work. Mingw (whatever was current on Soureforge a few days ago)įor debugging this problem in Dr. The static libraries and +/- stripping the symbols) Inkscape (from trunk, but the prepackaged binaries won't run in Dr.Memory either. (Note, this is not the actual test I want, which is a real run, but it demonstrates that inkscape does not work in Dr.Memory even for its simplest mode.) What version of the product are you using? On what operating system? Windows XP SP3 Where, of course, Dr.Memory isn't very useful!Īnd it did NOT produce the expected ldmp file, in fact, it produced nothing at all in dynamorio\logs What is the expected output? What do you see instead? Inkscape should run normally and exit, emitting the version number. leaks_only -no_count_leaks -no_track_allocs (Call stack in the results is up to 23 layers deep, going to frames 200 didn't help.) Tried the series of extra flags from "tips" and the program did not run to completion until: Otherwise there was a linker conflict concerning "invalid_argument". To use static libraries it was necessary to change in the inkscape source in file path_manipulator.c build inkscape on Windows using mingw (with symbols not stripped and the two static libraries used) What steps will reproduce the problem? 1.
0 kommentar(er)
