This would be good to add to the docs on using the Windows builds.
Bryce
On Fri, 18 Jun 2004, Bob Jamison wrote:
bulia byak wrote:
The bug is not present in builds up to and including 0406131800. It is present in builds 0406140200 and beyond.
Yeah, that's useful, but by backtrace I actually mean a GDB backtrace as described here:
http://inkscape.org/report_bugs.php
However for this to work you'll need a build compiled with debug info. If you don't compile your builds I wonder if we can provide unstripped auto builds for windows? (ishmal? mrchapp?)
I put a fresh unstripped .exe here:
http://troi.titan-aeu.com/~rjamison/inkscape/files/inkscape.zip
...just the .exe, not the whole package.
GDB can be obtained at http://www.cygwin.com , but this one is easier to fetch and use: http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download
It would be good for all of our Win32 testers to have a copy of this. Instead of double-clicking, type
"gdb inkscape.exe"
then "run"
If Inkscape crashes, type either "bt" or "where", which will give the information that we need. Emailing that to the list would be invaluable.
Bob
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel