When I was developing a new Morphic layout policy (in Squeak before there was
Pharo, but I imagine it still applies), I found numerous bugs relating to
bounds and layout methods and the order they get called in various
circumstances; bounds & layout is a poorly documented, fragile part of Morphi
Pharo-users] What is the craziest bug you ever face
Hi guys
During the DSU workshop we were brainstorming about what are the most
difficult bugs we faced and what are the conceptual tools that would have
helped you.
Stef
and occasionally memory leaks
werner
On 03/10/2017 04:02 PM, werner kassens wrote:
Hi Stephane,
bugs i found difficult to debug are eg (1) red cross of death bugs in
morphs, (2) bugs that are not visible any more because they are caught
and dealt with in the wrong place and then produce wrong
Hi Stephane,
bugs i found difficult to debug are eg (1) red cross of death bugs in
morphs, (2) bugs that are not visible any more because they are caught
and dealt with in the wrong place and then produce wrong results instead
of errors, and (3) bugs in iterative algos that work eg with #while
Yeah, that sounds right. The debugger needed to be able to step through lines
of code like normal (to debug the logic framework) as well as to step
through search steps (to debug programs written in the framework) defined in
terms of the system semantics (since bugs could be in either program or
fr
I understand well your point :)
On Thu, 09 Mar 2017 21:30:21 +0100, Dale Henrichs
wrote:
The attached screnshot illustrates why I like having text instead of
pngs ... being able to highlight the association value (-5.00->5.00) is
very useful when identifying the entries >in a btree as
The attached screnshot illustrates why I like having text instead of
pngs ... being able to highlight the association value (-5.00->5.00) is
very useful when identifying the entries in a btree associated with the
association (the entries at 13, 16,19, and 22)...
On 03/09/2017 11:34 AM, Dale
we were talking during the workshop and on the simple things to help.
- watch points with history of the value.
- stop if the value of an instance variable is getting irregular i.e.,
= you get integer and suddenly inside you get a float!
1 1 1 1 2 3 4 2 2 1 1 12 2 3 32 1 1 1 1 22
On Thu, 09 Mar 2017 20:53:48 +0100, Evan Donahue
wrote:
I actually have a whole class of bugs and elements of a very Pharo-y
solution.
I do a lot of work in a logic programming framework. Being a logic
programming framework, it does not execute the code you write in a
start-to-finish manner,
I should add that users of the logic framework from non-smalltalk languages
were very impressed by the potential.
Evan
--
View this message in context:
http://forum.world.st/What-is-the-craziest-bug-you-ever-face-tp4937984p4938040.html
Sent from the Pharo Smalltalk Users mailing list archive a
nice ideas!
Stef,
One of the things that I do all of the time when trying to debug
particularly difficult problems is to keep a "bug notebook". My "bug
notebook" is a text file where I record >information gleaned from an
inspector intermixed with comments, code and observations...
I'
I actually have a whole class of bugs and elements of a very Pharo-y
solution.
I do a lot of work in a logic programming framework. Being a logic
programming framework, it does not execute the code you write in a
start-to-finish manner, but executes a few lines here, then jumps around and
execute
Stef,
One of the things that I do all of the time when trying to debug
particularly difficult problems is to keep a "bug notebook". My "bug
notebook" is a text file where I record information gleaned from an
inspector intermixed with comments, code and observations...
I've attached an examp
Thanks you all.
The idea is that we want to see how we cn improve our debugging arsenal.
So it is important that your scenario give use some hints.
It is difficult to convey what we are really looking for :)
Hi guys
During the DSU workshop we were brainstorming about what are the most
diff
I don't think my reply will be anything useful, but as to me the most
craziest bug is metabug, i.e. when
system doesn't provides any means to debug things. :)
As for regular bugs .. it is quite hard to remember anything i wasn't able
to deal with, given enough time & effort, and then emphasize sin
2017-03-09 12:36 GMT+01:00 Stephane Ducasse :
> Hi guys
>
> During the DSU workshop we were brainstorming about what are the most
> difficult bugs we faced and what are the conceptual tools that would have
> helped you.
>
> Stef
>
https://pharo.fogbugz.com/f/cases/14332/use-ast-not-parseTree-so-w
For me it was when I was making the CPP library. CPP for those that do not
know is a library I made that allows Pharo to control a C++ application.
Its a very simple IPC bridge using shared memory mapped files.
I was surprised how easy it was to make it from the C++ side
Pharo side was a different
Hi guys
During the DSU workshop we were brainstorming about what are the most
difficult bugs we faced and what are the conceptual tools that would have
helped you.
Stef
18 matches
Mail list logo