Hi,
I missed (2nd time) the tech talk of yesterday.
Truth is that I’m running trying to getting everything ready for release and I
completely forget about it :(
So, I think best is just to skip last month’s tech-talk (it was already delayed
once) and focus in current’s one (and in releasing)
> On 5 Apr 2017, at 09:17, Esteban Lorenzano wrote:
>
> Hi,
>
> I missed (2nd time) the tech talk of yesterday.
> Truth is that I’m running trying to getting everything ready for release and
> I completely forget about it :(
>
> So, I think best is just to skip last month’s tech-talk (it w
Branch: refs/heads/6.0
Home: https://github.com/pharo-project/pharo-core
Commit: 0bb790cd74c3d0007c988699cf60e1675a1649a3
https://github.com/pharo-project/pharo-core/commit/0bb790cd74c3d0007c988699cf60e1675a1649a3
Author: Jenkins Build Server
Date: 2017-04-05 (Wed, 05 Apr 2017
Branch: refs/tags/60459
Home: https://github.com/pharo-project/pharo-core
Hi guys.
I could not accept your explanation because I have test which works on
latest squeakVM and not works on latest pharoVM. Try filein attachment and
check it on both VMs. Test not depends on any difference between squeak and
pharo images. You run it on both systems (not only VM's).
I found t
Branch: refs/tags/60460
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/6.0
Home: https://github.com/pharo-project/pharo-core
Commit: 9138e4ac13e0c23ba5b0c1335ff0adec36dec998
https://github.com/pharo-project/pharo-core/commit/9138e4ac13e0c23ba5b0c1335ff0adec36dec998
Author: Jenkins Build Server
Date: 2017-04-05 (Wed, 05 Apr 2017
Using the April 03 VM (the "latest" that was on Apr 03).
The vm is way more stable (this is the first crash in two active days, which is
record for me), so maybe the main cause of the problem has been fixed, but not
all causes.
I am also downloading latest (Apr 04) VM.
There is no crash dump, bu
Can confirm that the latest (Apr 4) VM crashes too.
I am not sure on what code this is crashing, but I am experiencing some odd
behavior from metalinks, so maybe I broke something there (I was using
metalinks a lot before the crash)... will investigate further.
Peter
On Wed, Apr 05, 2017 at 0
explicit call to garbage collect crashes the image (crash.dmp attached),
so I think that in this case I somehow corrupted the image (with metalinks
presumably)
On Wed, Apr 05, 2017 at 03:39:39PM +0200, Peter Uhnak wrote:
> Can confirm that the latest (Apr 4) VM crashes too.
>
> I am not sure on
Branch: refs/heads/6.0
Home: https://github.com/pharo-project/pharo-core
Commit: 142da6254d4c122f4f302064aff12ca489e5460b
https://github.com/pharo-project/pharo-core/commit/142da6254d4c122f4f302064aff12ca489e5460b
Author: Jenkins Build Server
Date: 2017-04-05 (Wed, 05 Apr 2017
Branch: refs/tags/60461
Home: https://github.com/pharo-project/pharo-core
Or if you want yet another crash in fresh image and latest vm...
(no crash.dmp of course)
Unhandled exception at 0x0048B197 in Pharo.exe: 0xC005: Access violation
reading location 0x0075.
registers
EAX=003F EBX=00ADCA14 ECX=0071 EDX=00ADD241 ESI=00372000 EDI=0071
EIP=0048B1
Eliot Miranda-2 wrote
> On Tue, Apr 4, 2017 at 10:00 AM, Denis Kudriashov <
> dionisiydk@
> >
> wrote:
>
>>
>> 2017-04-04 18:45 GMT+02:00 Esteban Lorenzano <
> estebanlm@
> >:
>>
>>> > I think you are wrong because I check it carefully in Squeak and I
>>> found it on github https://github.com/
Just in case anyone is not aware, you can auto-subscribe
to Issues that you comment on.
http://help.fogcreek.com/subscriptions-receive-notifications-for-changes-to-cases-and-wikis/
cheers -ben
Hi Ben,
On Thu, Apr 06, 2017 at 09:03:58AM +0800, Ben Coman wrote:
> Just in case anyone is not aware, you can auto-subscribe
> to Issues that you comment on.
>
> http://help.fogcreek.com/subscriptions-receive-notifications-for-changes-to-cases-and-wikis/
>
> cheers -ben
Many thanks for point t
16 matches
Mail list logo
