Grim reaper make Menguard hit

Hello,

Surely allready have seen that but memguard catch sometime memguard hit from Grim Reaper itself.....

On AOS4.1U2 and Sam:


MEMGUARD HIT - "reaper.task" (5cac6320)
in FreeVec(5A103000 [, 0]). Memory already freed
0: 5a103000 5c595e50 00000000 01ca97c4 5a103000 00000109 01daa368 01daa3dc
8: 01359480 5aaa80d0 0000000c 000000fd 42004024 00000000 ffffffff ffffffff
16: 7ffe5b00 5ff924d0 5c595eb0 01dbda96 00004000 5fffa800 5ff9a000 5ff983c0
24: 01dbd806 00000000 5ac61044 01dbd806 5aad8850 7fe2b9b8 7fe2b9a0 5c595e50
----> 01ca97c4 : "Kickstart/kernel" segment 0001 offset 497c0
----> 01daa368 : "Kickstart/kernel" segment 0001 offset 14a364
----> 01daa3dc : "Kickstart/kernel" segment 0001 offset 14a3d8
----> 01dbda96 : "Kickstart/kernel" segment 0001 offset 15da92
----> 01dbd806 : "Kickstart/kernel" segment 0001 offset 15d802
----> 01dbd806 : "Kickstart/kernel" segment 0001 offset 15d802
LR 0178a5c4 : "Kickstart/petunia.library.kmod" segment 0000 offset 0f60
CTR 6f3dd9c8 : "MemGuard" segment 0005 offset 89c0

Stack backtrace:
----> 0178a5c4 : "Kickstart/petunia.library.kmod" segment 0000 offset 0f60
----> 01415848 : "Kickstart/kernel" segment 0000 offset 15844
----> 6f3d5f74 : "MemGuard" segment 0005 offset 0f6c
----> 014271ec : "Kickstart/kernel" segment 0000 offset 271e8
----> 0150ad64 : "Kickstart/dos.library.kmod" segment 0000 offset 1b520
----> 01436290 : "Kickstart/kernel" segment 0000 offset 3628c
----> 01436310 : "Kickstart/kernel" segment 0000 offset 3630c

Disassembly:
0178a5c0: 4e800421 bctrl
0178a5c4: 813f000c lwz r9,12(r31)
0178a5c8: 800900ac lwz r0,172(r9)
0178a5cc: 7c0903a6 mtctr r0
0178a5d0: 807f000c lwz r3,12(r31)

@Mrodfr

I'd be more interested to know which 68K program was running at the time of the crash....

Simon

@Rigo

Hum, this is a good question

And apparently, I'm the only one because this problem seemed to be new for you (Aos4 team).


I haven't thousand of 68k program running all the time and as this memguard hit arrive more or less often, maybe tooldeamons 68k is the problem..... (but I will check more carefully next time in front of my SAM).

Yes, I can't live without tooldeamons on AOS4......

- Could AOS4 developpers team add tooldeamons as a main part of AOS4 (like kingCON clone actually tested) ???

That mean expand the wb menus by the user...

@Mrodfr

I didn't check lately but last time Toolsdaemon similar facility was included by standard into AOS since 3.5. IIRC it's driven by an ARexx script.

@abalaban + Mrodfr
AddMenu.rexx

@all

Do someone know if It's possible to make a tooldeamons clone, for AOS4, without the need to patch something (as tooldeamons do that on AOS3.x) and with all the features of toolsdeamons) ????

NOTE: I'm on the SAM and waiting the memguard hit came (nothing untill now).

@Mrodfr

see @TSK's remark,
That arexx script should handle adding user tool entrys just fine and without hacking into the system (i believe)

btw: Is that Hugh Laurie in your avatar?

@Mrodfr

That might be the reason why the Reaper can't kill programs any more since OS4.1.2 without causing endless recoverable 01000000F crashes and I have to reboot.

BTW. Toolsdeamon exists for OS4. I have used it since the start!

@Deniil

I don't know, I have sometime or often this kind of error during the use on AOS4.1U2.

Only memguard show the problem, but I don't know if really tooldeamons (68k) because I have used AOS yesterday during one hour (and with tooldeamons and memguard) and not seen this error.

BTW, where I can found toolsdaemons for AOS4 ????
(I'm verry interested)...

@Raziel

I have seen that my new avatar have a lot of interest

@Mrodfr

seeing the trace you sent it *is* clearly a 68k program that caused it because of petunia.library being on top of the stack frames... If ToolsDaemon is the only 68k thing you are running on your system then it *is* the culprit. And BTW using the arexx script mentionned by TSK isn't a hack at all (which I'm not sure ToolsDaemon was not), I really can't see why you don't want to use it ?? Do you have two features ToolsDaemon has and which can't be reproduced by using the script ??

@abalaban

As deniil said that toolsdaemons exist for AOS4, I could use it.

No need to make new settings at all, just replace 68k by AOS4 version. I'm waiting his answer impatiently !!

As you said, It's surely toolsdaemon 68k but yesterday, I have used one hour my SAM with toolsdaemons and memguard and not seen the memguard hit, I have a little doubt now....

@Mrodfr

Well, I'm not 100% sure the Toolsdaemon I use are an OS4/PPC executable, but it works fine. I think it is the updated version for use with OS3.9. this version uses the new arexx commands to add menues to Workbnech instead of that nasty hack the old versions had to use.

Using ARexx to add WB menus is the new non-hacky way, no matter if you use Toolsdaemon-OS3.9 or the ARexx script directly.

About the Reaper: Toolsdaemon isn't crashing for me and I doubt it is the reason SabreMSN crashes too. But the strange 68k stack traces the Reaper has given me, followed by endless recoverable 0100000F after SabreMSN crashing is annoying.

@Deniil

Quote:

I don't know the things you said about toolsdaemons, I'm surprised !!

I haven't sabreMSN who crash on my SAM. just sometime little difficulties for the connection....

you have received an email from me... (hum, your mailbox is full).....

@Mrodfr

probably you already have it patched (otherwise it shouldn't work at all on AOS4.x) but in case, you have to install this patch

http://aminet.net/util/boot/ToolsDaemon22.lha

using as base the 2.1a components in this archive

http://aminet.net/util/boot/ToolsDaemon21a.lha

@Mrodfr

Quote:

Then you must be using my old one. Try this daniel onyxsoft se instead. (Do NOT repost this with the at-sign, please.)