I have several issues using gitfiletree, which in turn has issues with
metacello trying to fetch git info about my git branch locally which I
tracked back to OSProcess not executing on my macos.
This started to happen as soon as I updated to latest XCODE and installed
its latest command tools, any
More bad luck I’m afraid. What can I do next?
Program received signal SIGSEGV, Segmentation fault.
0xb8c0b92d in ?? ()
(gdb) p (void)printCallStack()
Cannot access memory at address 0x
(gdb)
> On Oct 30, 2015, at 08:11, Esteban Lorenzano wrote:
>
> you can type
>
> p (void)printCall
Hi,
Is there a version of Seaside that works on Pharo5?
Uko
What I would like is access to the GPIO pins from Pharo…. It is possible from
Scratch so someone (i am to stupid to do this) could maybe hack that into Pharo?
Tim
> On 30 Oct 2015, at 16:22, Tim Hendriks wrote:
>
> Pharo5 works with fine with the squeak vm in Jessie. No error’s and much
> fa
Pharo5 works with fine with the squeak vm in Jessie. No error’s and much
faster. Didn’t test it thoroughly.
Tim
> On 26 Oct 2015, at 16:41, Attila Magyar wrote:
>
> Hi Torsten,
>
> Have you tried the cogvm on the Pi? It is much faster than the stack vm. If
> I remember correctly, I used this
Improve it and tweak it as much as you like, it was mainly intended as a
demonstrator of how to use the Roassal spec plugin. So as long as that part
remains clear, the cooler the tool the better it is :-).
> On Oct 30, 2015, at 10:24, Peter Uhnák wrote:
>
> Thanks Johan, I'll take a look.
>
No idea, but your visualizations are gorgeous!
Alexandre
> On Oct 30, 2015, at 7:48 AM, Peter Uhnák wrote:
>
> Hi,
>
> is it possible to programatically change the width of Playground/Inspector
> panes?
>
> Currently if I want one pane bigger I have to resize both which wastes a lot
> of s
you can type
p (void)printCallStack()
then you will have the active stack when crash happened. Is often a lot more
useful than the trace of the vm.
Esteban
> On 29 Oct 2015, at 19:03, Johan Fabry wrote:
>
>
> OK, back with access to the Ubuntu machine, I reproduced the crash when
> runnin
Peter,
Adding the feedback generation into makes the API even more
complicated, because you'd have to ar least pass a String as a fourth
parameter.
So we'd end up with:
assertExecuting: aBlock with: listOfArguments resultsIn:
expectedResult otherwise: failureString.
... and if you - like m
On 29/10/15 16:35, Esteban A. Maringolo wrote:
As some already know I'm working in the new GLORP port from VW to Pharo.
Are you generating the port with rewrite rules?
Stephan
10 matches
Mail list logo