On Tue, Mar 06, 2018 at 11:49:14AM +0100, Sabine Manaa wrote:
> Hi,
>
> I can report the following:
>
> The problem with the Buffer overflow remains also with OSProcess.
> Also with the normal vm (https://get.pharo.org ).
>
> Summary: I have buffer overflow crashes with my application on Linux.
What about sometime mid-May?
On 28 February 2018 at 19:10, Stephane Ducasse
wrote:
> Or 24-25 of May
> Or 31 - 1 June?
>
> On Wed, Feb 28, 2018 at 6:09 PM, Stephane Ducasse
> wrote:
> > Hi guys
> >
> > many people are asking when and where
There is a new Pharo build available!
The status of the build #660 was: SUCCESS.
The Pull Request #1037 was integrated: "21508-Integrate-Calypso-0103"
Pull request url: https://github.com/pharo-project/pharo/pull/1037
Issue Url: https://pharo.fogbugz.com/f/cases/21508
Build Url:
Nice work!
Doru
> On Mar 6, 2018, at 5:05 PM, Denis Kudriashov wrote:
>
> Hi.
>
> With latest version of Commander and Calypso we will have all shortcuts
> explorable and configurable in Settings Browser:
>
>
>
> Currently it uses command class name and class
Silly me.
I have no idea how to update this library. I thought it would be a file. I've
used Monticello years ago in Squeak - however trying to load this repository
into Pharo 6.1-64 is impossible. Invariably I end up with an undefined symbol
and a couple of undismissable progress dialogs.
Hi,
aioEnable et al should really check the fd argument against FD_SETSIZE
and answer error codes that get tested in clients. See two messages below:
On Tue, Mar 6, 2018 at 2:49 AM, Sabine Manaa wrote:
> Hi,
>
> I can report the following:
>
> The problem with the
Le 06/03/2018 à 04:19, Mariano Martinez Peck a écrit :
> Hi guys,
>
Hi!
> Thanks for Guillermo Polito we now have 64 bits support for
> OSSubprocess. You can see the required changes in this PR [1].
Cool :)
I made a
> branch called `support64bits` so that you can help us test it even if CI
>
> Cyril,
>
> For development I tend to use Metacello locking instead of hard-wired
> dependencies in the BaselineOf and that works very well --- it
> completely avoids the need to edit a baseline for development purposes
> and this approach works really well for me ... perhaps we can discuss
>
Le 06/03/2018 à 17:05, Denis Kudriashov a écrit :
> Hi.
>
> With latest version of Commander and Calypso we will have all shortcuts
> explorable and configurable in Settings Browser:
>
>
>
> Currently it uses command class name and class comment for presentation.
> We can improve it in future
On 03/06/2018 06:21 AM, Guillermo Polito wrote:
Hi Dale!
On Mon, Mar 5, 2018 at 8:07 PM, Dale Henrichs
> wrote:
On 03/05/2018 09:07 AM, Guillermo Polito wrote:
On the other side, there is the fact
There is a new Pharo build available!
The status of the build #659 was: SUCCESS.
The Pull Request #1036 was integrated: "21507-remove-SugsSmalltalkEditorContext"
Pull request url: https://github.com/pharo-project/pharo/pull/1036
Issue Url: https://pharo.fogbugz.com/f/cases/21507
Build
> On 6 Mar 2018, at 16:04, ci-pharo-ci-jenki...@inria.fr wrote:
>
> There is a new Pharo build available!
>
> The status of the build #657 was: FAILURE.
>
> The Pull Request #1024 was integrated: "21491 Simplify
> #testAllButFirstNElements and #testAllButLastNElements"
> Pull request
There is a new Pharo build available!
The status of the build #658 was: SUCCESS.
The Pull Request #1024 was integrated: "21491 Simplify
#testAllButFirstNElements and #testAllButLastNElements"
Pull request url: https://github.com/pharo-project/pharo/pull/1024
Issue Url:
So I made pull request for new Calypso version.
It modifies #loadCalypso method to fix versions of all dependencies using
locking statements.
I checked it for Pharo 6. It works fine.
https://github.com/pharo-project/pharo/pull/1037
2018-03-05 20:25 GMT+01:00 Dale Henrichs
There is a new Pharo build available!
The status of the build #657 was: FAILURE.
The Pull Request #1024 was integrated: "21491 Simplify
#testAllButFirstNElements and #testAllButLastNElements"
Pull request url: https://github.com/pharo-project/pharo/pull/1024
Issue Url:
Hi Dale!
On Mon, Mar 5, 2018 at 8:07 PM, Dale Henrichs <
dale.henri...@gemtalksystems.com> wrote:
>
>
> On 03/05/2018 09:07 AM, Guillermo Polito wrote:
>
>> On the other side, there is the fact that Metacello baselines are so far
>> nice to describe release project dependencies, but they are not
Seems to me aioEnable somehow triggers this.
It maintains buffers of size FD_SETSIZE (1024 on Linux)*, so an fd
parameter** >= that, could probably trigger such an error.
Maybe you could put a halt in whichever method in OSSubprocess/OSProcess
calls the primitive triggered when condition occurs,
Hi Sabine,
have you tried with a 64bits version of Pharo (with a recent VM, i.e.
newer than the 6.1 vm)? I use the 5.0-201801170946, for example.
If, by chance, you manage to create a script provoking the segfault,
that may really help.
Thierry
2018-03-06 11:49 GMT+01:00 Sabine Manaa
There is a new Pharo build available!
The status of the build #656 was: SUCCESS.
The Pull Request #1032 was integrated: "21505-update-README-md [skip ci]"
Pull request url: https://github.com/pharo-project/pharo/pull/1032
Issue Url: https://pharo.fogbugz.com/f/cases/21505
Build Url:
There is a new Pharo build available!
The status of the build #655 was: SUCCESS.
The Pull Request #1009 was integrated: "21474 More cleanups in
Compression-Tests"
Pull request url: https://github.com/pharo-project/pharo/pull/1009
Issue Url: https://pharo.fogbugz.com/f/cases/21474
Build
Hi,
I can report the following:
The problem with the Buffer overflow remains also with OSProcess.
Also with the normal vm (https://get.pharo.org ).
Summary: I have buffer overflow crashes with my application on Linux.
The same code runs without problems on MacOS and on Windows.
I have the same
There is a new Pharo build available!
The status of the build #654 was: SUCCESS.
The Pull Request #1020 was integrated: "21485 Use assert:equals: and other
small cleanups in StringTest"
Pull request url: https://github.com/pharo-project/pharo/pull/1020
Issue Url:
22 matches
Mail list logo