Smalltalk › Gemtalk › GLASS

#encodeUsing: segfault

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

GLASS mailing list

#encodeUsing: segfault

Hi

I don't know if Johan already reported this. During ESUG we found out
that we could segfault a gem with:

aString encodeUsing: nil

I don't have a GemStone installation at hand so I can't check if this
has been fixed in the mean time.

Cheers
Philippe
_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

GLASS mailing list

Re: #encodeUsing: segfault

This was tried on a gemstone 3.1.0.6.
Did not try this on 3.2 yet…

Johan

> On 21 Jul 2015, at 09:05, Philippe Marschall via Glass <[hidden email]> wrote:
>
> Hi
>
> I don't know if Johan already reported this. During ESUG we found out
> that we could segfault a gem with:
>
> aString encodeUsing: nil
>
> I don't have a GemStone installation at hand so I can't check if this
> has been fixed in the mean time.
>
> Cheers
> Philippe
> _______________________________________________
> Glass mailing list
> [hidden email]
> http://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

Richard Sargent

Re: #encodeUsing: segfault

Administrator

In reply to this post by GLASS mailing list

GLASS mailing list wrote

Hi

I don't know if Johan already reported this. During ESUG we found out
that we could segfault a gem with:

aString encodeUsing: nil

I don't have a GemStone installation at hand so I can't check if this
has been fixed in the mean time.

The first version containing a fix for this is 3.3 (yet to be released). It will throw an argument type exception.

The work-around is, of course, obvious. Provide an appropriate Array as the argument.

Cheers
Philippe
_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

GLASS mailing list

Re: #encodeUsing: segfault

In reply to this post by GLASS mailing list

On 07/21/2015 02:44 AM, Johan Brichau via Glass wrote:
> This was tried on a gemstone 3.1.0.6.
> Did not try this on 3.2 yet…

Thanks for the report!
I can reproduce this in 3.1.0.6, and in 3.2.7, but not in the latest 3.3
build. It looks like we've fixed it, but not yet in released product.

Regards,

-Martin

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

GLASS mailing list

Re: #encodeUsing: segfault

In reply to this post by GLASS mailing list

Hey Philippe!

I have been out for personal reasons the last two weeks, and now I am
back ... with an email backlog ... but I'm back ...

This rings a bell and I seem to think that it is fixed in 3.3... but I
will double check and let you know ...

Dale

On 07/21/2015 12:05 AM, Philippe Marschall via Glass wrote:

> Hi
>
> I don't know if Johan already reported this. During ESUG we found out
> that we could segfault a gem with:
>
> aString encodeUsing: nil
>
> I don't have a GemStone installation at hand so I can't check if this
> has been fixed in the mean time.
>
> Cheers
> Philippe
> _______________________________________________
> Glass mailing list
> [hidden email]
> http://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass