Hi andrei
Do you use a particular Wallet object?
it was in one of the tests. I put a halt into the coinFor: into2:
What image are you using? Pharo5.0 Latest update: #50759
Can you fuel out and send the stack if you get this error again?
I will try to reproduce it and send it to you. Stef
Cheers, Andrei
Stef
PS: Yes I know I'm the stupider guy in the world because I criticise the wonderful GT tools and I should not because it is not acceptable :)
Le 3/6/16 à 22:01, Andrei Chis a écrit :
Hi Stef,
Can you provide a way to load or access the entire code of your example?
Cheers, Andrei
On Fri, Jun 3, 2016 at 9:43 PM, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote:
Hi
I'm debugging a simple algo for a first exercises in Pharo future book and I get stepToSendOrReturn
DNU when using the debugger. :((((((((((((((((((((((((((((((((((((
You see I would really like in Pharo that we get new tools only when there are better than the old
ones. I still could not see how GTDebugger helps me debugging faster my programs.
Personally the fact that GT debugger can show bytecodes or can be extended is not in the critical path.
My critical path is that I can debug Pharo programs and now I cannot.
I also did not see any comments on the multiple complaints about the funky place for the buttons.
So to me GTDebugger is a disappointement.
Here is the kind of code I'm debugging so this is not that complex nor implying concurrency or whatever complex.
coinsFor: aValue into2: accuWallet
| accu | self halt. [ accu := accuWallet money. accu < aValue ] whileTrue: [ | big | big := self biggest. [ big > (aValue - accu) ] whileTrue: [ big := self biggestBelow: big ]. self removeCoin: big. accuWallet addCoin: big ]. ^ accuWallet
Stef