Image freeze when deprecated:transformWith: is used

[labordep]

I find a problem when I'm using Object>>deprecated:transformWith: .
Download the zip file to have a code to import into a new Pharo image for reproduce it :

Do the unit test MyClassTest>>testName, the image is freezing. I found no possibility to debug or quit, I'm forced to kill the pharo process.

This is a basic code and I'm using the Object>>deprecated:transformWith: as in ClassDescription>>definition example.

name
	"Example of deprecated rewrite from ClassDescription>>definition"

	self
		deprecated: #name
		transformWith: '`@receiver name:' -> '`@receiver id:'.

	^id

And the test :

testName

	| myClass |
	myClass := MyClass new.
	self assert: myClass name.

My config :

• Windows 11 Pro
• Pharo-11.0.0+build.545 (64 Bit)

To reproduce import this code and see MyClass-Tests package with the test :
MyClass-Tests.zip

[labordep]

@tinchodias find a way to explore :

When this checkbox is uncheck : there is a window with an error at the execution of the test :

[labordep]

And when the checkbox is checked, the freeze is here :

[MarcusDenker]

Just looking at the code:
the colons are nit correct: "@receiver name:" --> should be "@receiver name", same for id.

[MarcusDenker]

it freezes I think due to #name on classes being used very very deep in the system, if the rename goes wrong it will call that faulty method for sure during error reporting, leading to a loop.

[labordep]

Thanks @MarcusDenker, but we have the same problem in Bloc (pharo-graphics/Bloc#207) for another message (not name).

[labordep]

It should be better to open a debugger instead of freeze :) I tried to interrupt an eventually loop but this is not working (I have tried MAJ CTRL + . )

[MarcusDenker]

But the debugger calls #name again, which leads to the same error, which leads to the same error, which leads to the same error...

[MarcusDenker]

If I try this on an example that is not #name of Class (which is very special, as it is called a lot and especially during error handling), it works for me as it should. I get a SytnaxErrorDebugger, I can close it, just as expected.