Page 1 of 1

Bug in Type command?

Posted: Sat Feb 02, 2013 11:18 pm
by blmara
Hi! While testing my program I installed MemGuard (v.1.15) and used it without any arguments. The output was catched with Sashimi. Then I started to get a MemGuard hit shown below every time I use AmigaOS Type Command (for example, using for displaying the Startup-Sequence). A bug in the Type command?
Hidden Text - Click to Show :
MEMGUARD HIT - [7] "type" (5c297b80)
rear wall damaged -- 5E6DE680 = AllocVec(20, 00001000)
0: 02206fd0 5e6f2d70 5dd01290 02963588 5e6de680 0200f030 00000034 00000000
8: 48842082 7f1309c8 02206064 02a7b386 28844088 5e6e6680 00000000 62759b70
16: 5f8de380 7fd40310 00000002 02b30000 5d4a59e0 02b30000 02b30000 00000000
24: 00000002 6ff8f000 0000002c 5f8de380 00000014 5e6de680 5d49d9e0 5d49d9b4
----> 02206fd0 : "newlib.library.kmod" segment 0000 offset 2e0c
----> 02963588 : "kernel" segment 0001 offset 43584
----> 0200f030 : "kernel" segment 0000 offset f02c
----> 7f1309c8 : "Work:Commands/MemGuard" segment 0005 offset 89c0
----> 02206064 : "newlib.library.kmod" segment 0000 offset 1ea0
----> 02a7b386 : "kernel" segment 0001 offset 15b382
----> 7fd40310 : "type" segment 0005 offset 0308
----> 02b30000 : "rtg.library" segment 0001 offset 1f1c
----> 02b30000 : "rtg.library" segment 0001 offset 1f1c
----> 02b30000 : "rtg.library" segment 0001 offset 1f1c
----> 5d49d9e0 : "type" segment 0004 offset 0028
----> 5d49d9b4 : "type" segment 0004 offset fffffffc
LRa 02206f30 : "newlib.library.kmod" segment 0000 offset 2d6c
CTRa 7f130950 : "Work:Commands/MemGuard" segment 0005 offset 8948
LR 02206fec : "newlib.library.kmod" segment 0000 offset 2e28
CTR 7f1309c8 : "Work:Commands/MemGuard" segment 0005 offset 89c0

Stack backtrace:
----> 02206fec : "newlib.library.kmod" segment 0000 offset 2e28
----> 02207070 : "newlib.library.kmod" segment 0000 offset 2eac
----> 7fd40104 : "type" segment 0005 offset 00fc
----> 02117e8c : "dos.library.kmod" segment 0000 offset 22a08
----> 02043054 : "kernel" segment 0000 offset 43050
----> 020430d4 : "kernel" segment 0000 offset 430d0

Disassembly:
02206fe8: 4e800421 bctrl
02206fec: 7e8da378 mr r13,r20
02206ff0: 4bfff8a8 b 0x2206898
02206ff4: 9421ffc0 stwu r1,-64(r1)
02206ff8: 7c0802a6 mflr r0
Marko

Re: Bug in Type command?

Posted: Mon Feb 04, 2013 7:34 am
by kas1e
Confirmed on latest betas and added as BZ #8238

Re: Bug in Type command?

Posted: Tue Apr 30, 2013 9:37 am
by kas1e
fixed too

Re: Bug in Type command?

Posted: Wed May 01, 2013 9:43 am
by trixie
MemGuard is a nice little tool, isn't it? :-)

Re: Bug in Type command?

Posted: Wed May 01, 2013 2:23 pm
by kas1e
@Trixie

I go through all os components by it, and almost all what i find out (there was 4 or 5), are fixed. But together with memguard i also use debug-kernel with munge, and that helps even more.