Debugger freezes

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Debugger freezes

Günther Schmidt
Hi,

whenever I'm calling

ArtistBroker>>objectWithKey: aKey

        ^self objects at: aKey ifAbsentPut: [self makeObjectForKey: Key]

the debugger comes up, because

ArtistBroker>>makeObjectForKey: aKey

is not yet defined.

OK so far, but then the debugger freeze, well actually all of Dolphin does.

It doesn't occur in other situations when the debugger comes up.

Also

ArtistBroker>>objects

        objects ifNil: [objects := WeakIdentityDictionary new].
        ^objects

initializes a WeakIdentityDictionary.

Could that be related?
I'm running DST XP Pro 5.1.4 on Windows XP SP2

Günther


Reply | Threaded
Open this post in threaded view
|

Re: Debugger freezes

Schwab,Wilhelm K
Günther,

> whenever I'm calling
>
> ArtistBroker>>objectWithKey: aKey
>
>     ^self objects at: aKey ifAbsentPut: [self makeObjectForKey: Key]
>
> the debugger comes up, because
>
> ArtistBroker>>makeObjectForKey: aKey
>
> is not yet defined.

Clearly defining it is in order, but that is not really your question.


> OK so far, but then the debugger freeze, well actually all of Dolphin does.
>
> It doesn't occur in other situations when the debugger comes up.

Does control-break get out of it?  Either way, my first thought is the
#printOn: is giving you trouble.  There is a method called
#debugPrintString(??) that you can use to make the debugger's life
easier if that is the case.

Have a good one,

Bill


--
Wilhelm K. Schwab, Ph.D.
[hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: Debugger freezes

Günther Schmidt
Bill,

Bill Schwab wrote:
>
> Does control-break get out of it?  Either way, my first thought is the
> #printOn: is giving you trouble.  There is a method called
> #debugPrintString(??) that you can use to make the debugger's life
> easier if that is the case.
>

1. what's control-break? (asking totally embarrassed :-( )

2. how come #printOn: would cause a problem? Just asking because I never
had any trouble like this before.


Thanks

Günther


Reply | Threaded
Open this post in threaded view
|

Re: Debugger freezes - control break

Günther Schmidt
In reply to this post by Schwab,Wilhelm K
Bill,

sorry, yes, control break does get me out of it.



Günther


Reply | Threaded
Open this post in threaded view
|

Re: Debugger freezes

Esteban A. Maringolo-3
In reply to this post by Günther Schmidt
Günther Schmidt escribió:
> Bill,
>
> Bill Schwab wrote:
>
>>
>> Does control-break get out of it?  Either way, my first thought is the
>> #printOn: is giving you trouble.  There is a method called
>> #debugPrintString(??) that you can use to make the debugger's life
>> easier if that is the case.

> 1. what's control-break? (asking totally embarrassed :-( )

Press Ctrl+Break, it halts the current process.

> 2. how come #printOn: would cause a problem? Just asking because I never
> had any trouble like this before.

The debugger tries to print the object involved in the program stack
(receivers, inst. vars, etc). If a problem occurs in the printOn: it
may get recursive causing another wallkback, and so on.

Best regards.

--
Esteban.