[postgis-devel] Call for 1.5.2 release

[Paul Ramsey]

Fixing that error and moving on it gets a little deeper...

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000040
0x00007fff87d34180 in strlen ()
(gdb) bt
#0  0x00007fff87d34180 in strlen ()
#1  0x0000000100b8c6a4 in g_strdup ()
#2  0x0000000100b1e9c5 in value_collect_string ()
#3  0x0000000100125ec2 in gtk_list_store_set_valist_internal ()
#4  0x00000001001276cd in gtk_list_store_set_valist ()
#5  0x00000001001277bb in gtk_list_store_set ()
#6  0x000000010000b7a8 in pgui_create_file_table [inlined] () at
/Users/pramsey/Code/postgis-1.5-svn/loader/shp2pgsql-gui.c:2454
#7  0x000000010000b7a8 in pgui_create_main_window [inlined] () at
/Users/pramsey/Code/postgis-1.5-svn/loader/shp2pgsql-gui.c:2271
#8  0x000000010000b7a8 in main (argc=1, argv=0x7fff5fbff5c0) at
shp2pgsql-gui.c:2587


P

On Tue, Aug 10, 2010 at 4:38 PM, Paul Ramsey <pramsey at cleverelephant.ca> wrote:
> Yeah, the GUI is problematic, as the changes are very substantial, and
> will need lots of testing. I just now tried to build and run on OS/X
> and got
>
> shp2pgsql-gui(77973) malloc: *** error for object 0x100e0e960: pointer
> being freed was not allocated
> *** set a breakpoint in malloc_error_break to debug
>
> Not sure if folks have done a build and test on Win32 yet. For 1.5.2
> it would be nicer to keep the current GUI, no?
>
> P.
>
> (Of course, I have a reason to not want to change things, having just
> finished a couple workshops full of screenshots of the *old* GUI.)
>
> On Mon, Aug 2, 2010 at 3:45 AM, Mark Cave-Ayland
> <mark.cave-ayland at siriusit.co.uk> wrote:
>> Paul Ramsey wrote:
>>
>>> I am fine with a release. Let me know when you feel the branch has risen
>>> to the level of cutting a tar ball, or do you think we are there right now?
>>>
>>> P.
>>
>> The changelog looks reasonably sensible, although I didn't realise until
>> just now that Mark's shp2pgsql GUI changes had been merged into 1.5 branch.
>> IMO that's quite a large change for a bugfix release on an existing branch.
>>
>> The other issue, of course, is that yesterday there was an API change in the
>> 9.0 analyze function:
>> http://archives.postgresql.org/pgsql-committers/2010-08/msg00013.php. We
>> should code up a fix for this before cutting the release.
>>
>>
>> ATB,
>>
>> Mark.
>>
>> --
>> Mark Cave-Ayland - Senior Technical Architect
>> PostgreSQL - PostGIS
>> Sirius Corporation plc - control through freedom
>> http://www.siriusit.co.uk
>> t: +44 870 608 0063
>>
>> Sirius Labs: http://www.siriusit.co.uk/labs
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>>
>