FE and Copy/Paste crash

[zzd10h]

No, except to send the log of course

Maybe that something is wrong in my partition, OK. But even by booting on the CD, it fails.

Is somebody could try by booting directly on the CD on his X1000, please ?

Thank you

[xenic]

No, except to send the log of course

Maybe that something is wrong in my partition, OK. But even by booting on the CD, it fails.

Is somebody could try by booting directly on the CD on his X1000, please ?

Thank you

I tested ContextMenu copy/paste when I booted from the OS4.1 FE CD. I opened the SYS:Prefs window, right-clicked on the AHI icon and selected copy from the Contextmenu. Then I opened the RAM: window, right-clicked an empty area in the RAM: window and selected paste from the Contextmenu. AHI was copied into the RAM: window. Sorry, but I am unable to reproduce your problem even when booting from the CD.

[zzd10h]

Thank you for your test,
hopefully that Raziel have the same problem than me.

@TonyW
if you need a tester or more elements...
Thank you

[zzd10h]

Problem solved by removing "SERIAL DEBUGLEVEL=5 MUNGE" from os4_commandline in CFE !

I thought that these parameters were only used by kernel.debug ?
At least under 4.1.6, it seems that it was the case.

under 4.1.6
My LittleBrother was OK with this line and standard kernel
but it crashed with this line and debug kernel.
(I solved this problem in my program since months )

BUT

1) Is the FE standard kernel a debug kernel ?

2) Is it normal that MUNGE and/or DEBUGLEVEL and/or SERIAL make crash Copy/Paste from ContextMenu ?


Regarding "New text file bug", not better, still crashs !

[zzd10h]

@TonyW
Are you around ?

Thx

[xenic]

Problem solved by removing "SERIAL DEBUGLEVEL=5 MUNGE" from os4_commandline in CFE

I thought that these parameters were only used by kernel.debug ?

My system has had: "os4commandline=DEBUGLEVEL=5 SERIAL" since the day I bought it. I would guess that it's just the "MUNGE" that is causing the crash. Maybe MUNGE (whatever that is) needs to be fixed.

P.S. There is SYS:Kickstart/kernal.debug in my FE installation but it's not used in the Kicklayout.

[salass00]

My system has had: "os4commandline=DEBUGLEVEL=5 SERIAL" since the day I bought it. I would guess that it's just the "MUNGE" that is causing the crash. Maybe MUNGE (whatever that is) needs to be fixed.

If "munge" option causes a program to crash then that program is buggy and should be fixed. Possible reasons for munge causing a program to crash is if it reads from uninitialised memory or memory that has already been freed.

The whole point of "munge" option is to cause bugged programs to crash in a visible manner so no, it should not be "fixed".

[xenic]

My system has had: "os4commandline=DEBUGLEVEL=5 SERIAL" since the day I bought it. I would guess that it's just the "MUNGE" that is causing the crash. Maybe MUNGE (whatever that is) needs to be fixed.

If "munge" option causes a program to crash then that program is buggy and should be fixed. Possible reasons for munge causing a program to crash is if it reads from uninitialised memory or memory that has already been freed.

The whole point of "munge" option is to cause bugged programs to crash in a visible manner so no, it should not be "fixed".

Then I guess that means that ContextMenu copy/paste does have a bug

[salass00]

Then I guess that means that ContextMenu copy/paste does have a bug

Yes, most likely it does.

[kas1e]

@Xenic
Btw, you probably remember that in some of the dopus5 bugreports on our repo i write "bug can be reproduced with munge only", what mean that even if without munge there is no crashes/dsi/isi, etc, but triggered when we use "munge" kernel's feature, then bug in reality is here. "munge" just help us to find it , while when we not use munge, bug just hide itself.