Hi folks, I know the aim is to close bugs not open them, but I've found another "crashes it every time i do it" bug. Steps to crash inkscape are as follows:
create a rectangle, switch to path mode, convert it to path, select the 2 nodes on one side and hit the + a couple of times so you have one side divided into 4 sections. select 2 of the new nodes, and split the path, now select the same 2 nodes and hit tje join path at selectd nodes button, and voila, error box.
error on win2k reads: **ERROR**: file nodepath.cpp:line2778(void sp_nodepath_subpath_close(SPNodeSubPath*)): assertion failed: (sp->first->cpde == ART_MOVETO) aborting...
after which it bombs out.
entered in tracker as bug #900635
cheers
John
__________________________________ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools
On Thu, 19 Feb 2004, John Cliff wrote:
Hi folks, I know the aim is to close bugs not open them, but I've found another "crashes it every time i do it" bug.
Yeah don't be shy about opening new bugs, especially for crash bugs.
We can still achieve our goal for 0.38 if we get swamped with bug reports, if we close enough old bugs, so be as prolific as you like with new ones. :-)
The biggest thing that helps is that the bugs are repeatable, so the "crashes it every time I do it" bugs are extremely helpful.
Bryce
John Cliff wrote:
Hi folks, I know the aim is to close bugs not open them, but I've found another "crashes it every time i do it" bug. Steps to crash inkscape are as follows:
create a rectangle, switch to path mode, convert it to path, select the 2 nodes on one side and hit the + a couple of times so you have one side divided into 4 sections. select 2 of the new nodes, and split the path, now select the same 2 nodes and hit tje join path at selectd nodes button, and voila, error box.
error on win2k reads: **ERROR**: file nodepath.cpp:line2778(void sp_nodepath_subpath_close(SPNodeSubPath*)): assertion failed: (sp->first->cpde == ART_MOVETO) aborting...
after which it bombs out.
entered in tracker as bug #900635
cheers
John
Simple answer: I will check this out. It is likely something extremently simple.
Geek answer: ;-) Possibly splitting the subpath changed the direction of one of the pieces, so what was ->first is now ->last. We just need to make sure that the first node of a subpath is a MOVETO.
Bob
John Cliff wrote:
Hi folks, I know the aim is to close bugs not open them, but I've found another "crashes it every time i do it" bug. Steps to crash inkscape are as follows:
create a rectangle, switch to path mode, convert it to path, select the 2 nodes on one side and hit the + a couple of times so you have one side divided into 4 sections. select 2 of the new nodes, and split the path, now select the same 2 nodes and hit tje join path at selectd nodes button, and voila, error box.
error on win2k reads: **ERROR**: file nodepath.cpp:line2778(void sp_nodepath_subpath_close(SPNodeSubPath*)): assertion failed: (sp->first->cpde == ART_MOVETO) aborting...
after which it bombs out.
entered in tracker as bug #900635
cheers
John
Got it. (I think) When splitting open a closed nodepath by removing segment(s), the first node of the resulting path must be an ART_MOVETO. Since the segment behind it is gone, it can't be anything else! ;) Yaaaay.
Committed. This should show up on the next build.
Bob
On Fri, 20 Feb 2004, Bob Jamison wrote:
Got it. (I think) When splitting open a closed nodepath by removing segment(s), the first node of the resulting path must be an ART_MOVETO. Since the segment behind it is gone, it can't be anything else! ;) Yaaaay.
Committed. This should show up on the next build.
Congrats! Good fix.
Bryce
Bob, I've just got back from two weeks away and I'm having a heap of trouble with the latest win builds and with the official win 32 download. Your automated build site now jumps from December to 20 Feb. Can you give access to the builds between 10 Feb and 20 Feb please? This will allow me to pinpoint some of the troubles I'm having .....I hope, before I start posting much.
Just as a taste I'm attaching a shot of a coffee cup shown on win build of 10 Feb (my latest auto build that works) and the official win32 build.
vellum
vellum wrote:
Bob, I've just got back from two weeks away and I'm having a heap of trouble with the latest win builds and with the official win 32 download. Your automated build site now jumps from December to 20 Feb. Can you give access to the builds between 10 Feb and 20 Feb please? This will allow me to pinpoint some of the troubles I'm having .....I hope, before I start posting much.
Just as a taste I'm attaching a shot of a coffee cup shown on win build of 10 Feb (my latest auto build that works) and the official win32 build.
vellum
Well, as you might have noticed, the project files have been in severe flux recently, with both the addition of new material, and the reorganization of existing things. For the last couple of weeks, just keeping it buildable has been a full time task.
Those builds you speak of might be lost. During my website cleanup, I moved those to a backup directory, intending them to be available as 'archive' builds. Now I can't find them! Maybe they were backed up Friday evening; if so, I will return them to the site. I would like to organize them the way I do my other projects: daily builds for a week, weekly builds for a month, monthly builds for a year.
Last night, I had time to spend on actually running Inkscape. This is uncommon for me; I work on several software projects where I am well familiar with the code, but never actually use the stuff. So last night I found a couple of usability bugs, and several unnecessary warnings, and got rid of all but one.
Bob
Bob wrote:
Well, as you might have noticed, the project files have been in severe flux recently, with both the addition of new material, and the reorganization of existing things. For the last couple of weeks, just keeping it buildable has been a full time task.
I have been away for two weeks so I have not noticed the "severe flux" but I can certainly sympathise with keeping anything like this on the rails. And thanks again for doing these auto builds-maybe behind the scenes they are not quite 'auto' eh? But I really appreciate them.
Those builds you speak of might be lost. During my website cleanup, I moved those to a backup directory, intending them to be available as 'archive' builds. Now I can't find them! Maybe they were backed up Friday evening; if so, I will return them to the site. I would like to organize them the way I do my other projects: daily builds for a week, weekly builds for a month, monthly builds for a year.
Not to worry too much about the backups. They were primarily for completion of my files and the current build (26 Feb)has fixed some of my problems, such as non-saving of SVG extensions on files, and not seeing SVG files at all so being unable to open them.
Last night, I had time to spend on actually running Inkscape. This is uncommon for me; I work on several software projects where I am well familiar with the code, but never actually use the stuff. So last night I found a couple of usability bugs, and several unnecessary warnings, and got rid of all but one.
The coffee cup bug I mentioned earlier is still present. It may not be important since it only appears when opening SVG files prepared from other programs. However, these files were opened OK in earlier incarnations of Inkscape so it may be a simple fix.
Let me know if you want another example.
vellum
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
vellum wrote:
I have been away for two weeks so I have not noticed the "severe flux" but I can certainly sympathise with keeping anything like this on the rails. And thanks again for doing these auto builds-maybe behind the scenes they are not quite 'auto' eh? But I really appreciate them.
Actually, the cron scheduler emails me a daily transcript of the output of the build script. I usually just look at the end of the file for the word "Done" to make sure it worked. If it did not work, and there are some fixes or features that someone might want to see, then , yeah, I am the 'auto'.
For example, that build problem that bulia had. It broke last night's build, too. So I will likely tweak the thing, and re-run it.
The coffee cup bug I mentioned earlier is still present. It may not be important since it only appears when opening SVG files prepared from other programs. However, these files were opened OK in earlier incarnations of Inkscape so it may be a simple fix.
Let me know if you want another example.
vellum
Ted or Nathan might be better at rendering problems than me. Looks like it might be a numeric sign problem.
Bob
participants (4)
-
Bob Jamison -
Bryce Harrington -
John Cliff -
vellum