Re: [Inkscape-devel] win32. Print seems to be broken

I've added a page with this info to the website:
http://www.inkscape.org/report_bugs.php
Bryce
On Wed, 28 Apr 2004, bulia byak wrote:
> >Hmmm, any more info on this. Can you get a stack trace or something
> >similar? There has been a few changes, notably the adding of extension
> >properties into the print subsystem. I think that is the biggest change
> >there, so I'm a touch concerned.
>
> Let me suggest a few guidelines for users on how to report bugs:
>
> If the bug you report to the list is not fixed promptly, this may mean
> developers cannot reproduce it, or cannot understand your description, or
> are simply too busy with other things. Be persistent. As the original
> reporter, you are the person most interested in fixing it, so if your first
> report had no effect, you must not let it drop. There are many things you
> can do to push your bug closer to fixing:
>
> 1. Submit the bug to the tracker. Don't wait for someone else to do it. It's
> important, otherwise your report will be quickly forgotten. (But check the
> tracker first, your bug may be already there.)
>
> 2. Submit complete information: version, platform, locale, steps to
> reproduce, sample file(s), screenshots.
>
> 3. If this is a crash, it's important to submit a backtrace. Use gdb to get
> a backtrace by running
>
> gdb <path to inkscape executable>
>
> and then from within gdb
>
> run <parameters>
>
> When the program crashes, type at the gdb prompt
>
> bt
>
> and send us the output. All of this can be done on Windows too, the Windows
> binary of gdb is available from http://www.mingw.org/download.shtml.
>
> 4. If you really want the bug to be fixed, try to find out the exact point
> in time when the bug appeared. At the very least, test old Inkscape
> versions. To get a narrower and more useful estimate, use backdated CVS
> checkouts (the -D switch) to find the most recent date on which the CVS was
> is OK, and also the first date on which it is broken. Then we can make a
> diff between these two dates to figure out the reason. If you manage to find
> the day of breakage and if that day's diff is big (which is possible, given
> the rate of checkins we're having on average), try to narrow it down to a
> few hours. For example:
>
> cvs -d:ext:<your sf login>@cvs.sf.net:/cvsroot/inkscape checkout
> -D"2004-04-04 12:00" inkscape
>
> will give you the CVS as it was on that date at midday. I think this should
> work with anonymous CVS access too.
>
> _________________________________________________________________
> MSN Premium includes powerful parental controls and get 2 months FREE*
> http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 10g.
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel@...
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>
>

Thread view

>Hmmm, any more info on this. Can you get a stack trace or something
>similar? There has been a few changes, notably the adding of extension
>properties into the print subsystem. I think that is the biggest change
>there, so I'm a touch concerned.
Let me suggest a few guidelines for users on how to report bugs:
If the bug you report to the list is not fixed promptly, this may mean
developers cannot reproduce it, or cannot understand your description, or
are simply too busy with other things. Be persistent. As the original
reporter, you are the person most interested in fixing it, so if your first
report had no effect, you must not let it drop. There are many things you
can do to push your bug closer to fixing:
1. Submit the bug to the tracker. Don't wait for someone else to do it. It's
important, otherwise your report will be quickly forgotten. (But check the
tracker first, your bug may be already there.)
2. Submit complete information: version, platform, locale, steps to
reproduce, sample file(s), screenshots.
3. If this is a crash, it's important to submit a backtrace. Use gdb to get
a backtrace by running
gdb <path to inkscape executable>
and then from within gdb
run <parameters>
When the program crashes, type at the gdb prompt
bt
and send us the output. All of this can be done on Windows too, the Windows
binary of gdb is available from http://www.mingw.org/download.shtml.
4. If you really want the bug to be fixed, try to find out the exact point
in time when the bug appeared. At the very least, test old Inkscape
versions. To get a narrower and more useful estimate, use backdated CVS
checkouts (the -D switch) to find the most recent date on which the CVS was
is OK, and also the first date on which it is broken. Then we can make a
diff between these two dates to figure out the reason. If you manage to find
the day of breakage and if that day's diff is big (which is possible, given
the rate of checkins we're having on average), try to narrow it down to a
few hours. For example:
cvs -d:ext:<your sf login>@cvs.sf.net:/cvsroot/inkscape checkout
-D"2004-04-04 12:00" inkscape
will give you the CVS as it was on that date at midday. I think this should
work with anonymous CVS access too.
_________________________________________________________________
MSN Premium includes powerful parental controls and get 2 months FREE*
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines

I've added a page with this info to the website:
http://www.inkscape.org/report_bugs.php
Bryce
On Wed, 28 Apr 2004, bulia byak wrote:
> >Hmmm, any more info on this. Can you get a stack trace or something
> >similar? There has been a few changes, notably the adding of extension
> >properties into the print subsystem. I think that is the biggest change
> >there, so I'm a touch concerned.
>
> Let me suggest a few guidelines for users on how to report bugs:
>
> If the bug you report to the list is not fixed promptly, this may mean
> developers cannot reproduce it, or cannot understand your description, or
> are simply too busy with other things. Be persistent. As the original
> reporter, you are the person most interested in fixing it, so if your first
> report had no effect, you must not let it drop. There are many things you
> can do to push your bug closer to fixing:
>
> 1. Submit the bug to the tracker. Don't wait for someone else to do it. It's
> important, otherwise your report will be quickly forgotten. (But check the
> tracker first, your bug may be already there.)
>
> 2. Submit complete information: version, platform, locale, steps to
> reproduce, sample file(s), screenshots.
>
> 3. If this is a crash, it's important to submit a backtrace. Use gdb to get
> a backtrace by running
>
> gdb <path to inkscape executable>
>
> and then from within gdb
>
> run <parameters>
>
> When the program crashes, type at the gdb prompt
>
> bt
>
> and send us the output. All of this can be done on Windows too, the Windows
> binary of gdb is available from http://www.mingw.org/download.shtml.
>
> 4. If you really want the bug to be fixed, try to find out the exact point
> in time when the bug appeared. At the very least, test old Inkscape
> versions. To get a narrower and more useful estimate, use backdated CVS
> checkouts (the -D switch) to find the most recent date on which the CVS was
> is OK, and also the first date on which it is broken. Then we can make a
> diff between these two dates to figure out the reason. If you manage to find
> the day of breakage and if that day's diff is big (which is possible, given
> the rate of checkins we're having on average), try to narrow it down to a
> few hours. For example:
>
> cvs -d:ext:<your sf login>@cvs.sf.net:/cvsroot/inkscape checkout
> -D"2004-04-04 12:00" inkscape
>
> will give you the CVS as it was on that date at midday. I think this should
> work with anonymous CVS access too.
>
> _________________________________________________________________
> MSN Premium includes powerful parental controls and get 2 months FREE*
> http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 10g.
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel@...
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>
>