On Jun 24, 2010, at 4:38 05PM, Mariano Martinez Peck wrote:



On Thu, Jun 24, 2010 at 10:31 AM, Henrik Sperre Johansen <henrik.s.johansen@veloxit.no> wrote:
 On 24.06.2010 09:51, Mariano Martinez Peck wrote:
I have seen this error several times. We don't know where it cames from, but yes, there is a problem.

In my case, I always notice in the same situation: when saving an image, one of the methods I was most recentrly edditing, replaces the sintax with part of the string of the image name.

Exactly the same situation Torsten had here.

So....yes, I had this problem a lot of times. I cannot reproduce it always, it just happens sometimes.

Cheers

Mariano
Sounds a lot like some other tool is modifying the source file position directly rather than operating on a read-only copy...
We could either:
- Find out which, fix the sender (could take some time to find the right one)
- Ensure position is at end before writing the image name to file as part of the string. (easy to do, but problem still remain other places which may assume position is at end)



Henry, I know NOTHING about it, but I just saw this issue: http://code.google.com/p/pharo/issues/detail?id=2547

maybe something related or just non sense?

cheers

mariano
 
Just nonsense :P

Come to think of it, you don't happen to have two vm's running the same image, do you?

That would be another thing causing this sort of error to arise...

Cheers,
Henry