RC1 image build failure

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

RC1 image build failure

Schwab,Wilhelm K
Hello all,

Whatever is happening, it keeps happening, and on two different machines, but both Ubuntu 9.10, FWIW.  Attached is a shot of the whatever-it's-called window; the promised emergency evaluator does not appear (not that I would know what to do with it<g>).  Comparing SharedQueue with SharedQueue2 might be interesting; with luck, there will simply be a missing method??

Bill


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

rc1-no-debugger.png (138K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: RC1 image build failure

Nicolas Cellier
2009/11/4 Schwab,Wilhelm K <[hidden email]>:

> Hello all,
>
> Whatever is happening, it keeps happening, and on two different machines, but both Ubuntu 9.10, FWIW.  Attached is a shot of the whatever-it's-called window; the promised emergency evaluator does not appear (not that I would know what to do with it<g>).  Comparing SharedQueue with SharedQueue2 might be interesting; with luck, there will simply be a missing method??
>
> Bill
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

1) Yeah, SharedQueue2 does not share same public protocol and that
sounds like a bug...

(SharedQueue selectors difference: SharedQueue2 selectors) reject: [:e
| (SharedQueue organization categoryOfElement: e) beginsWith:
'private'].
-> an IdentitySet(#flushAllSuchThat: #nextOrNilSuchThat: #flush)

We might also wanter to filter out unsent ones:
(SharedQueue selectors difference: SharedQueue2 selectors) reject: [:e
| ((SharedQueue organization categoryOfElement: e) beginsWith:
'private') or: [(SystemNavigation default allCallsOn: e) isEmpty]]


2) I find it strange your Smalltalk doesNotUnderstand: #findElementOrNil:

Did you load some changes related to FasterSets or is your image
damned corrupted ?
Try (Smalltalk findElementOrNil: #Object) and tell us the result.

Nicolas

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: RC1 image build failure

Schwab,Wilhelm K
Nicolas,

I doubt the images are corrupt, unless the download is somehow damaged.  #findElementOrNil: works; the problem is more likely that the missing protocol in SharedSet2 lead to an unrecoverable meltdown.  My question is how it worked as long as it did???

Bill




-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Nicolas Cellier
Sent: Tuesday, November 03, 2009 7:28 PM
To: [hidden email]
Subject: Re: [Pharo-project] RC1 image build failure

2009/11/4 Schwab,Wilhelm K <[hidden email]>:

> Hello all,
>
> Whatever is happening, it keeps happening, and on two different machines, but both Ubuntu 9.10, FWIW.  Attached is a shot of the whatever-it's-called window; the promised emergency evaluator does not appear (not that I would know what to do with it<g>).  Comparing SharedQueue with SharedQueue2 might be interesting; with luck, there will simply be a missing method??
>
> Bill
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

1) Yeah, SharedQueue2 does not share same public protocol and that sounds like a bug...

(SharedQueue selectors difference: SharedQueue2 selectors) reject: [:e
| (SharedQueue organization categoryOfElement: e) beginsWith:
'private'].
-> an IdentitySet(#flushAllSuchThat: #nextOrNilSuchThat: #flush)

We might also wanter to filter out unsent ones:
(SharedQueue selectors difference: SharedQueue2 selectors) reject: [:e
| ((SharedQueue organization categoryOfElement: e) beginsWith:
'private') or: [(SystemNavigation default allCallsOn: e) isEmpty]]


2) I find it strange your Smalltalk doesNotUnderstand: #findElementOrNil:

Did you load some changes related to FasterSets or is your image damned corrupted ?
Try (Smalltalk findElementOrNil: #Object) and tell us the result.

Nicolas

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: RC1 image build failure

Nicolas Cellier
2009/11/4 Schwab,Wilhelm K <[hidden email]>:
> Nicolas,
>
> I doubt the images are corrupt, unless the download is somehow damaged.  #findElementOrNil: works; the problem is more likely that the missing protocol in SharedSet2 lead to an unrecoverable meltdown.  My question is how it worked as long as it did???
>
> Bill
>

I don't think you get the order right.
Follow the sender chain:

flushAllSuchThat: < flushNonKbdEvents < nextKeyboardEvent < keyboard < 4 senders
- onPrimitiveError: (your case)
- request: used by above message
- flushKeyboard 3 senders, does not fail because 99% of time there is
no event to flush
- tempCommand: < disabledCommandActions this one does not seem used

If you look at your stack trace, you'll see at:ifAbsent: fails first
(doesNotUnderstand: #findElementOrNil:)

Then onPrimitiveError: is triggered and cause a flushAllSuchThat:
which is not understood...

That is rare, and that is why it was not encountered before.

Thus I see 2 bugs:
- one rare bug in SharedQueue2 in Pharo-core
- (Smalltalk doesNotUnderstand: #findElementOrNil:) in your image to
be explained first

Nicolas

>
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Nicolas Cellier
> Sent: Tuesday, November 03, 2009 7:28 PM
> To: [hidden email]
> Subject: Re: [Pharo-project] RC1 image build failure
>
> 2009/11/4 Schwab,Wilhelm K <[hidden email]>:
>> Hello all,
>>
>> Whatever is happening, it keeps happening, and on two different machines, but both Ubuntu 9.10, FWIW.  Attached is a shot of the whatever-it's-called window; the promised emergency evaluator does not appear (not that I would know what to do with it<g>).  Comparing SharedQueue with SharedQueue2 might be interesting; with luck, there will simply be a missing method??
>>
>> Bill
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
> 1) Yeah, SharedQueue2 does not share same public protocol and that sounds like a bug...
>
> (SharedQueue selectors difference: SharedQueue2 selectors) reject: [:e
> | (SharedQueue organization categoryOfElement: e) beginsWith:
> 'private'].
> -> an IdentitySet(#flushAllSuchThat: #nextOrNilSuchThat: #flush)
>
> We might also wanter to filter out unsent ones:
> (SharedQueue selectors difference: SharedQueue2 selectors) reject: [:e
> | ((SharedQueue organization categoryOfElement: e) beginsWith:
> 'private') or: [(SystemNavigation default allCallsOn: e) isEmpty]]
>
>
> 2) I find it strange your Smalltalk doesNotUnderstand: #findElementOrNil:
>
> Did you load some changes related to FasterSets or is your image damned corrupted ?
> Try (Smalltalk findElementOrNil: #Object) and tell us the result.
>
> Nicolas
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: RC1 image build failure

Schwab,Wilhelm K
Nicolas,

If I have the order wrong, then I submit we have yet another bug: the text spilled onto my display reads in part: "Original error: MessageNotUnderstood: SharedQueue2>>flushAllSuchThat:."

You might be correct in flagging #findElementOrNil:, but the text suggests to me that this is a knock on effect to the SharedQueue2 deficiency.  Further supporting evidence includes that #findElementOrNil: works in the image, and SharedQueue2 is indeed missing methods relative to its task.

Either way, how do we fix this?

Bill


-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Nicolas Cellier
Sent: Tuesday, November 03, 2009 8:17 PM
To: [hidden email]
Subject: Re: [Pharo-project] RC1 image build failure

2009/11/4 Schwab,Wilhelm K <[hidden email]>:
> Nicolas,
>
> I doubt the images are corrupt, unless the download is somehow damaged.  #findElementOrNil: works; the problem is more likely that the missing protocol in SharedSet2 lead to an unrecoverable meltdown.  My question is how it worked as long as it did???
>
> Bill
>

I don't think you get the order right.
Follow the sender chain:

flushAllSuchThat: < flushNonKbdEvents < nextKeyboardEvent < keyboard < 4 senders
- onPrimitiveError: (your case)
- request: used by above message
- flushKeyboard 3 senders, does not fail because 99% of time there is no event to flush
- tempCommand: < disabledCommandActions this one does not seem used

If you look at your stack trace, you'll see at:ifAbsent: fails first
(doesNotUnderstand: #findElementOrNil:)

Then onPrimitiveError: is triggered and cause a flushAllSuchThat:
which is not understood...

That is rare, and that is why it was not encountered before.

Thus I see 2 bugs:
- one rare bug in SharedQueue2 in Pharo-core
- (Smalltalk doesNotUnderstand: #findElementOrNil:) in your image to be explained first

Nicolas

>
>
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of
> Nicolas Cellier
> Sent: Tuesday, November 03, 2009 7:28 PM
> To: [hidden email]
> Subject: Re: [Pharo-project] RC1 image build failure
>
> 2009/11/4 Schwab,Wilhelm K <[hidden email]>:
>> Hello all,
>>
>> Whatever is happening, it keeps happening, and on two different machines, but both Ubuntu 9.10, FWIW.  Attached is a shot of the whatever-it's-called window; the promised emergency evaluator does not appear (not that I would know what to do with it<g>).  Comparing SharedQueue with SharedQueue2 might be interesting; with luck, there will simply be a missing method??
>>
>> Bill
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
> 1) Yeah, SharedQueue2 does not share same public protocol and that sounds like a bug...
>
> (SharedQueue selectors difference: SharedQueue2 selectors) reject: [:e
> | (SharedQueue organization categoryOfElement: e) beginsWith:
> 'private'].
> -> an IdentitySet(#flushAllSuchThat: #nextOrNilSuchThat: #flush)
>
> We might also wanter to filter out unsent ones:
> (SharedQueue selectors difference: SharedQueue2 selectors) reject: [:e
> | ((SharedQueue organization categoryOfElement: e) beginsWith:
> 'private') or: [(SystemNavigation default allCallsOn: e) isEmpty]]
>
>
> 2) I find it strange your Smalltalk doesNotUnderstand: #findElementOrNil:
>
> Did you load some changes related to FasterSets or is your image damned corrupted ?
> Try (Smalltalk findElementOrNil: #Object) and tell us the result.
>
> Nicolas
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: RC1 image build failure

Nicolas Cellier
2009/11/4 Schwab,Wilhelm K <[hidden email]>:
> Nicolas,
>
> If I have the order wrong, then I submit we have yet another bug: the text spilled onto my display reads in part: "Original error: MessageNotUnderstood: SharedQueue2>>flushAllSuchThat:."
>
> You might be correct in flagging #findElementOrNil:, but the text suggests to me that this is a knock on effect to the SharedQueue2 deficiency.  Further supporting evidence includes that #findElementOrNil: works in the image, and SharedQueue2 is indeed missing methods relative to its task.

This message is misleading indeed.

>
> Either way, how do we fix this?
>
> Bill
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Nicolas Cellier
> Sent: Tuesday, November 03, 2009 8:17 PM
> To: [hidden email]
> Subject: Re: [Pharo-project] RC1 image build failure
>
> 2009/11/4 Schwab,Wilhelm K <[hidden email]>:
>> Nicolas,
>>
>> I doubt the images are corrupt, unless the download is somehow damaged.  #findElementOrNil: works; the problem is more likely that the missing protocol in SharedSet2 lead to an unrecoverable meltdown.  My question is how it worked as long as it did???
>>
>> Bill
>>
>
> I don't think you get the order right.
> Follow the sender chain:
>
> flushAllSuchThat: < flushNonKbdEvents < nextKeyboardEvent < keyboard < 4 senders
> - onPrimitiveError: (your case)
> - request: used by above message
> - flushKeyboard 3 senders, does not fail because 99% of time there is no event to flush
> - tempCommand: < disabledCommandActions this one does not seem used
>
> If you look at your stack trace, you'll see at:ifAbsent: fails first
> (doesNotUnderstand: #findElementOrNil:)
>
> Then onPrimitiveError: is triggered and cause a flushAllSuchThat:
> which is not understood...
>
> That is rare, and that is why it was not encountered before.
>
> Thus I see 2 bugs:
> - one rare bug in SharedQueue2 in Pharo-core
> - (Smalltalk doesNotUnderstand: #findElementOrNil:) in your image to be explained first
>
> Nicolas
>
>>
>>
>>
>> -----Original Message-----
>> From: [hidden email]
>> [mailto:[hidden email]] On Behalf Of
>> Nicolas Cellier
>> Sent: Tuesday, November 03, 2009 7:28 PM
>> To: [hidden email]
>> Subject: Re: [Pharo-project] RC1 image build failure
>>
>> 2009/11/4 Schwab,Wilhelm K <[hidden email]>:
>>> Hello all,
>>>
>>> Whatever is happening, it keeps happening, and on two different machines, but both Ubuntu 9.10, FWIW.  Attached is a shot of the whatever-it's-called window; the promised emergency evaluator does not appear (not that I would know what to do with it<g>).  Comparing SharedQueue with SharedQueue2 might be interesting; with luck, there will simply be a missing method??
>>>
>>> Bill
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>
>> 1) Yeah, SharedQueue2 does not share same public protocol and that sounds like a bug...
>>
>> (SharedQueue selectors difference: SharedQueue2 selectors) reject: [:e
>> | (SharedQueue organization categoryOfElement: e) beginsWith:
>> 'private'].
>> -> an IdentitySet(#flushAllSuchThat: #nextOrNilSuchThat: #flush)
>>
>> We might also wanter to filter out unsent ones:
>> (SharedQueue selectors difference: SharedQueue2 selectors) reject: [:e
>> | ((SharedQueue organization categoryOfElement: e) beginsWith:
>> 'private') or: [(SystemNavigation default allCallsOn: e) isEmpty]]
>>
>>
>> 2) I find it strange your Smalltalk doesNotUnderstand: #findElementOrNil:
>>
>> Did you load some changes related to FasterSets or is your image damned corrupted ?
>> Try (Smalltalk findElementOrNil: #Object) and tell us the result.
>>
>> Nicolas
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: RC1 image build failure

Nicolas Cellier
In reply to this post by Schwab,Wilhelm K
2009/11/4 Schwab,Wilhelm K <[hidden email]>:

> Nicolas,
>
> If I have the order wrong, then I submit we have yet another bug: the text spilled onto my display reads in part: "Original error: MessageNotUnderstood: SharedQueue2>>flushAllSuchThat:."
>
> You might be correct in flagging #findElementOrNil:, but the text suggests to me that this is a knock on effect to the SharedQueue2 deficiency.  Further supporting evidence includes that #findElementOrNil: works in the image, and SharedQueue2 is indeed missing methods relative to its task.
>
> Either way, how do we fix this?
>
> Bill
>

http://code.google.com/p/pharo/issues/detail?id=1408

>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Nicolas Cellier
> Sent: Tuesday, November 03, 2009 8:17 PM
> To: [hidden email]
> Subject: Re: [Pharo-project] RC1 image build failure
>
> 2009/11/4 Schwab,Wilhelm K <[hidden email]>:
>> Nicolas,
>>
>> I doubt the images are corrupt, unless the download is somehow damaged.  #findElementOrNil: works; the problem is more likely that the missing protocol in SharedSet2 lead to an unrecoverable meltdown.  My question is how it worked as long as it did???
>>
>> Bill
>>
>
> I don't think you get the order right.
> Follow the sender chain:
>
> flushAllSuchThat: < flushNonKbdEvents < nextKeyboardEvent < keyboard < 4 senders
> - onPrimitiveError: (your case)
> - request: used by above message
> - flushKeyboard 3 senders, does not fail because 99% of time there is no event to flush
> - tempCommand: < disabledCommandActions this one does not seem used
>
> If you look at your stack trace, you'll see at:ifAbsent: fails first
> (doesNotUnderstand: #findElementOrNil:)
>
> Then onPrimitiveError: is triggered and cause a flushAllSuchThat:
> which is not understood...
>
> That is rare, and that is why it was not encountered before.
>
> Thus I see 2 bugs:
> - one rare bug in SharedQueue2 in Pharo-core
> - (Smalltalk doesNotUnderstand: #findElementOrNil:) in your image to be explained first
>
> Nicolas
>
>>
>>
>>
>> -----Original Message-----
>> From: [hidden email]
>> [mailto:[hidden email]] On Behalf Of
>> Nicolas Cellier
>> Sent: Tuesday, November 03, 2009 7:28 PM
>> To: [hidden email]
>> Subject: Re: [Pharo-project] RC1 image build failure
>>
>> 2009/11/4 Schwab,Wilhelm K <[hidden email]>:
>>> Hello all,
>>>
>>> Whatever is happening, it keeps happening, and on two different machines, but both Ubuntu 9.10, FWIW.  Attached is a shot of the whatever-it's-called window; the promised emergency evaluator does not appear (not that I would know what to do with it<g>).  Comparing SharedQueue with SharedQueue2 might be interesting; with luck, there will simply be a missing method??
>>>
>>> Bill
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>
>> 1) Yeah, SharedQueue2 does not share same public protocol and that sounds like a bug...
>>
>> (SharedQueue selectors difference: SharedQueue2 selectors) reject: [:e
>> | (SharedQueue organization categoryOfElement: e) beginsWith:
>> 'private'].
>> -> an IdentitySet(#flushAllSuchThat: #nextOrNilSuchThat: #flush)
>>
>> We might also wanter to filter out unsent ones:
>> (SharedQueue selectors difference: SharedQueue2 selectors) reject: [:e
>> | ((SharedQueue organization categoryOfElement: e) beginsWith:
>> 'private') or: [(SystemNavigation default allCallsOn: e) isEmpty]]
>>
>>
>> 2) I find it strange your Smalltalk doesNotUnderstand: #findElementOrNil:
>>
>> Did you load some changes related to FasterSets or is your image damned corrupted ?
>> Try (Smalltalk findElementOrNil: #Object) and tell us the result.
>>
>> Nicolas
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: RC1 image build failure

Stéphane Ducasse
In reply to this post by Schwab,Wilhelm K

On Nov 4, 2009, at 1:55 AM, Schwab,Wilhelm K wrote:

> Nicolas,
>
> I doubt the images are corrupt, unless the download is somehow  
> damaged.


we never know.
So we should hunt that.

> #findElementOrNil: works; the problem is more likely that the  
> missing protocol in SharedSet2 lead to an unrecoverable meltdown.  
> My question is how it worked as long as it did???
>
> Bill
>
>
>
>
> -----Original Message-----
> From: [hidden email] [mailto:pharo-
> [hidden email]] On Behalf Of Nicolas Cellier
> Sent: Tuesday, November 03, 2009 7:28 PM
> To: [hidden email]
> Subject: Re: [Pharo-project] RC1 image build failure
>
> 2009/11/4 Schwab,Wilhelm K <[hidden email]>:
>> Hello all,
>>
>> Whatever is happening, it keeps happening, and on two different  
>> machines, but both Ubuntu 9.10, FWIW.  Attached is a shot of the  
>> whatever-it's-called window; the promised emergency evaluator does  
>> not appear (not that I would know what to do with it<g>).  
>> Comparing SharedQueue with SharedQueue2 might be interesting; with  
>> luck, there will simply be a missing method??
>>
>> Bill
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
> 1) Yeah, SharedQueue2 does not share same public protocol and that  
> sounds like a bug...
>
> (SharedQueue selectors difference: SharedQueue2 selectors) reject: [:e
> | (SharedQueue organization categoryOfElement: e) beginsWith:
> 'private'].
> -> an IdentitySet(#flushAllSuchThat: #nextOrNilSuchThat: #flush)
>
> We might also wanter to filter out unsent ones:
> (SharedQueue selectors difference: SharedQueue2 selectors) reject: [:e
> | ((SharedQueue organization categoryOfElement: e) beginsWith:
> 'private') or: [(SystemNavigation default allCallsOn: e) isEmpty]]
>
>
> 2) I find it strange your Smalltalk doesNotUnderstand:  
> #findElementOrNil:
>
> Did you load some changes related to FasterSets or is your image  
> damned corrupted ?
> Try (Smalltalk findElementOrNil: #Object) and tell us the result.
>
> Nicolas
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project