Johan,
I will double check that you are hitting a known bug (engineer not available at the moment).
To answer your upgrade question, the answer is yes you do need to go through the upgrade process.
When you restore from backup into 3.1.0.5, you get all of the changes to the executables, but you don't get any of the changes to the image ... depending upon the bugs fixed and the code paths that you have used (so far) you may not suffer from not having the matching Smalltalk code, but that doesn't mean there aren't problems lurking in the future.
Dale
----- Original Message -----
| From: "Johan Brichau" <
[hidden email]>
| To:
[hidden email]
| Sent: Tuesday, January 7, 2014 2:14:27 AM
| Subject: Re: [Glass] internal crashes
|
| Hi again,
|
| Going through the release notes of 3.1.0.3 I found that SEGV in
| GsSocket bug was fixed.
| Is this the bug I am hitting?
|
| Another question: does an upgrade from 3.1.0.2 to 3.1.0.5 require to
| go through all the upgrade steps like from 3.0 to 3.1 ?
| Ok, the release notes say so but I restored a backup from 3.1.0.2
| into a 3.1.0.5 and that seemed to work fine. But maybe I'm not aware
| of something.
|
| best regards
| Johan
|
| On 07 Jan 2014, at 10:50, Johan Brichau <
[hidden email]> wrote:
|
| > Hi,
| >
| > I'm getting quite frequent vm crashes on a 3.1.0.2 stone.
| > I attached two such gdb stack traces.
| > We are running on centos 6.4
| >
| > Is there a possibility to find out what is happening?
| > In the meantime, I will see to upgrade to 3.1.0.5
| >
| > cheers
| > Johan
| >
| >
| > <crash.log><crash2.log>
|
| _______________________________________________
| Glass mailing list
|
[hidden email]
|
http://lists.gemtalksystems.com/mailman/listinfo/glass|
_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Locked
crash.log (21K)