Hi folks
I've been away from development for a while, but recently checked out the current tree on the `April 200' release. The installation I had been using for production work hadn't been updated for some months, and the first difference I found was that the recent v.out.shape segfaulted (the old one worked OK - for me). I seem to recall there were some bug reports on this back about July or thereabouts, but no recent reports.
I'm not going to file a report on this because I've already fixed it here, but I would like to wait for some feedback on current experience of others before checking in.
David
On Sunday 06 January 2002 02:40, David D Gray wrote:
Hi folks
I've been away from development for a while, but recently checked out
the current tree on the `April 200' release.
Are you talking about 'releasebranch_11_april_2001_5_0_0' branch?
The installation I had been
using for production work hadn't been updated for some months, and the
first difference I found was that the recent v.out.shape segfaulted (the
old one worked OK - for me). I seem to recall there were some bug
reports on this back about July or thereabouts, but no recent reports.
I'm not going to file a report on this because I've already fixed it
here, but I would like to wait for some feedback on current experience
of others before checking in.
I checked in DBMI support before Christmas into 'MAIN' branch.
(you can export full table).
Is it problem in my new development version or in the old stable?
Radim
David
_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5
Hi Markus,
OK! I'll check in the changes. There seems to have been a lot of commenting out calls to free and other cleanup ops. I then find the segfault just moves to a `realloc' call - so, there seems to be some upstream overflow or similar, which I presume is responsible for many of the problems. I've moved the declaration of P_AREA *Area out to static which seems to work OK, but I still can't call `free()' on Area without getting a segfault. This isn't particularly good style and it's just a workaround but at least it moves us on a step.
David
Markus Neteler wrote:
[...]
For us here at IRST the current CVS version causes a lot of problems
(sorry to say this). If you just try
Spearfish location
v.out.shape roads
v.in.shape roads.shp
that's also not working. So we'll appreciate an update!
Best regards
Markus
Radim Blazek wrote:
On Sunday 06 January 2002 02:40, David D Gray wrote:
Hi folks
I've been away from development for a while, but recently checked out
the current tree on the `April 200' release.
Are you talking about 'releasebranch_11_april_2001_5_0_0' branch?
Yes.
The installation I had been
using for production work hadn't been updated for some months, and the
first difference I found was that the recent v.out.shape segfaulted (the
old one worked OK - for me). I seem to recall there were some bug
reports on this back about July or thereabouts, but no recent reports.
I'm not going to file a report on this because I've already fixed it
here, but I would like to wait for some feedback on current experience
of others before checking in.
I checked in DBMI support before Christmas into 'MAIN' branch.
(you can export full table).
Is it problem in my new development version or in the old stable?
It is probably a long-standing memory allocation problem - so - in both (?). I have still to get a working devel branch here, so I can't check, but as soon as I have, I'll check this module. I want to track down the memory problem in stable first though.
David