[GRASS-user] Re: Stack Dumpfile in WinGRASS installation with OSGEO4w

Markus Neteler neteler at osgeo.org
Tue Jul 27 01:24:45 EDT 2010


Monica,

I searched in the internet for such messages and came across this

http://readlist.com/lists/lists.sourceforge.net/mingw-msys/0/341.html

Perhaps giving you some idea?

Markus

On Mon, Jul 26, 2010 at 6:26 PM, Monica Buescu
<monicabuescu1985 at gmail.com> wrote:
> Greetings
> A new update from myu precvious message (from which I didn't receive any
> answer): I'm installing weekly snapshot from last Friday and I'm gettingh a
> lot of Stackdumpfile printed in my mingw window and I'm getting a Lot of
> errors while building dlls which means that a lot of binaries are not being
> created.
>
> On Fri, Jul 23, 2010 at 11:53 AM, Monica Buescu <monicabuescu1985 at gmail.com>
> wrote:
>>
>> Hi
>> Since I saw today a message from Helmut, stating that 19-07 Snapshot is to
>> be updated, I decided to install an earlier version (from June).
>> While I was installing GRASS i got a lot of :
>>     0 [main] sh 3880 open_stackdumpfile: Dumping stack trace to
>> sh.exe.stackdump
>>       0 [main] sh 960 open_stackdumpfile: Dumping stack trace to
>> sh.exe.stackdum                                        p
>>       0 [main] sh 2256 open_stackdumpfile: Dumping stack trace to
>> sh.exe.stackdu                                        mp
>>       0 [main] sh 3724 open_stackdumpfile: Dumping stack trace to
>> sh.exe.stackdu                                        mp
>>       0 [main] sh 772 open_stackdumpfile: Dumping stack trace to
>> sh.exe.stackdum                                        p
>>       0 [main] sh 2632 open_stackdumpfile: Dumping stack trace to
>> sh.exe.stackdu                                        mp
>>       0 [main] sh 3464 open_stackdumpfile: Dumping stack trace to
>> sh.exe.stackdu                                        mp
>>       0 [main] sh 2056 open_stackdumpfile: Dumping stack trace to
>> sh.exe.stackdu                                        mp
>> But I got a text stating that it was built without any errors.
>> What is happening? Is this a problem? (because in my first attempt nothing
>> was written in C:\osgeo4w\apps\grass and in second, without any change, it
>> wrote there)
>> Thanks
>> Monica
>
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
>


More information about the grass-user mailing list