Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
87 user(s) are online (79 user(s) are browsing Forums)

Members: 1
Guests: 86

hlt, more...

Support us!

Headlines

 
  Register To Post  

Need help to catch the bug of random lockups of LodePaint
Home away from home
Home away from home


See User information
For now LodePaint have strange bug on AOS4 (which not happenes on win32 and linux), which cause a random lockups. Its more or less random for me on peg2, but , as i can see, for RaserX bug happenes more or less stable.

So, i just do some editing and alt, and make lockup happenes, then reboot by magic combo, and "dumpdebugbuffer" say:

Quote:

Dump of context at 0x020991F0
Trap type: DSI exception
Machine State (raw): 0x0200F030
Machine State (verbose): [ExtInt on] [User] [FPU on] [IAT on] [DAT on]
Instruction pointer: in module kernel+0x00019F4C (0x01819F4C)
Crashed process: lodepaint (0x668551A0)
DSI verbose error description: Access not found in hash or BAT (page fault)
Access was a store operation
0: 66435FDC 64704DC0 39299480 66435FDC 66435FDC 00000000 00000020 00000010
8: 00000001 BCFF5F90 0181D87C 664351D0 28424122 63151240 00000004 80020021
16: 64704FC0 48424124 021B0000 00000000 00000000 021B69A6 020A31DA 00001000
24: 00000000 021B0000 00000000 EFFFE910 00000000 66435FDC 66435FD0 020A2BC8
CR: 88224148 XER: 00000003 CTR: 01819F58 LR: 018304EC
DSISR: 42000000 DAR: BCFF5F94

FP0 : 0000000068ACF056 0000000000000000 FF01000400000F00 4036000000000000
FP4 : 4024000000000000 403DCCCCC0000000 4052B33340000000 0000000068ACF056
FP8 : 0000000D00070009 0001FFFF0033000E EA2A2A2A2A2A2A2A 0000000000000000
FP12: 010000000000029B 0000000D00070009 0000000000000000 0000000000000000
FP16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP24: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP28: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPSCR: 8A004000

V0 - V30: all zeroes

VSCR: 00000000 VRSAVE: 00000000
Dump of context at 0xEFDAFBA0
Trap type: DSI exception
Machine State (raw): 0x0200F030
Machine State (verbose): [ExtInt on] [User] [FPU on] [IAT on] [DAT on]
Instruction pointer: in module kernel+0x00019F4C (0x01819F4C)
Crashed process: lodepaint (0x668551A0)
DSI verbose error description: Access not found in hash or BAT (page fault)
Access was a store operation
0: 66435FDC 64704DC0 39299480 66435FDC 66435FDC 00000000 00000020 00000010
8: 00000001 BCFF5F90 0181D87C 664351D0 28424122 63151240 00000004 80020021
16: 64704FC0 48424124 021B0000 00000000 00000000 021B69A6 020A31DA 00001000
24: 00000000 021B0000 00000000 EFFFE910 00000000 66435FDC 66435FD0 020A2BC8
CR: 88224148 XER: 00000003 CTR: 01819F58 LR: 018304EC
DSISR: 42000000 DAR: BCFF5F94

FP0 : FFF800008A004000 0000000000000000 FF01000400000F00 4036000000000000
FP4 : 4024000000000000 403DCCCCC0000000 4052B33340000000 0000000068ACF056
FP8 : 0000000D00070009 0001FFFF0033000E EA2A2A2A2A2A2A2A 0000000000000000
FP12: 010000000000029B 0000000D00070009 0000000000000000 0000000000000000
FP16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP24: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP28: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPSCR: 8A004000

V0 : 00000000000000000000000000010000 FFE5E9EFFFE5E9EFFFE5E9EFFFE5E9EF
V2 : FE01CD32FE01CD32FE01CD32FE0108F7 FE01CD32FE01CD32FE01CD32FE0108F7
V4 : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF E51BEF11E51BEF11E51BEF11E51BEF11
V6 : FE01E817FE01E817FE01E817FE01E817 00000000010101010202020203030303
V8 : 00000000000000000000000000000000 C936D52AC936D52AC936D52A08F709F6
V10: FFE5E9EFFFE5E9EFFFE5E9EFFFE5E9EF 00000000010101010202020203030303
V12: FE01E817FE01E817FE01E817FE01E817 00000000000000000000000000000000
V14: 001002120414061608180A1A0C1C0E1E 01000100010001000100010001000100
V16: FF000000FF000000FF000000FF000000 FFCACED6FFCACED6FFCACED6FF09090A
V18: 00000000000000000000000000000000 00000000000000000000000000000000
V20: 00000000000000000000000000000000 00000000000000000000000000000000
V22: 00000000000000000000000000000000 00000000000000000000000000000000
V24: 00000000000000000000000000000000 00000000000000000000000000000000
V26: 01010101010101010101010101010101 00000102030304050606070809090A0B
V28: 04040506070708090A0A0B0C0D0D0E0F 0C0C0D0E0F0F10111212131415151617
V30: 1818191A1B1B1C1D1E1E1F0001010203 FF000000FF000000FF000000FF000000
VSCR: 00010000 VRSAVE: 00000000

Registers pointing to code:
r10: module kernel at 0x0181D87C (section 0 @ 0x1D880)



Then i try one more time, and try to make lockup again, it was happens on absolutly different place of work, and after magic reset, dumpdebugbuffer say to me:

Quote:

Dump of context at 0x020991F0
Trap type: DSI exception
Machine State (raw): 0x0200F030
Machine State (verbose): [ExtInt on] [User] [FPU on] [IAT on] [DAT on]
Instruction pointer: in module kernel+0x00019F4C (0x01819F4C)
Crashed process: lodepaint (0x65EB9630)
DSI verbose error description: Access not found in hash or BAT (page fault)
Access was a store operation
0: 65DBAFDC 6519C910 3B595F3B 65DBAFDC 65DBAFDC 00000000 00000020 00000000
8: 00000001 DFFFAA20 0181D87C 65DBAB00 24448344 664F2240 651A5FFC 000F4FF8
16: 6519CC08 04000000 021B0000 00000000 00000000 021B69A6 020A31DA 00001000
24: 00000000 021B0000 00000000 EFFFE910 00000000 65DBAFDC 65DBAFD0 020A2BC8
CR: 88228348 XER: 40003E5C CTR: 01819F58 LR: 018304EC
DSISR: 42000000 DAR: DFFFAA24

FP0 : 0000000000000000 0000000000000000 407CA00000000000 0000000000000000
FP4 : 3FF0000000000000 0000000000000000 0000000000000000 0000000000000000
FP8 : 3FF0000000000000 0000000000000000 0000000000000000 0000000000000000
FP12: 406FE00000000000 40ED99A000000000 0000000000000000 0000000000000000
FP16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP24: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP28: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPSCR: 8A008000


V0 - V30 : all zeroes

VSCR: 00000000 VRSAVE: 00000000
Dump of context at 0xEFDCE7C0
Trap type: DSI exception
Machine State (raw): 0x0200F030
Machine State (verbose): [ExtInt on] [User] [FPU on] [IAT on] [DAT on]
Instruction pointer: in module kernel+0x00019F4C (0x01819F4C)
Crashed process: lodepaint (0x65EB9630)
DSI verbose error description: Access not found in hash or BAT (page fault)
Access was a store operation
0: 65DBAFDC 6519C910 3B595F3B 65DBAFDC 65DBAFDC 00000000 00000020 00000000
8: 00000001 DFFFAA20 0181D87C 65DBAB00 24448344 664F2240 651A5FFC 000F4FF8
16: 6519CC08 04000000 021B0000 00000000 00000000 021B69A6 020A31DA 00001000
24: 00000000 021B0000 00000000 EFFFE910 00000000 65DBAFDC 65DBAFD0 020A2BC8
CR: 88228348 XER: 40003E5C CTR: 01819F58 LR: 018304EC
DSISR: 42000000 DAR: DFFFAA24

FP0 : FFF800008A008000 0000000000000000 407CA00000000000 0000000000000000
FP4 : 3FF0000000000000 0000000000000000 0000000000000000 0000000000000000
FP8 : 3FF0000000000000 0000000000000000 0000000000000000 0000000000000000
FP12: 406FE00000000000 40ED99A000000000 0000000000000000 0000000000000000
FP16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP24: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP28: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPSCR: 8A008000

V0 : 00000000000000000000000000010000 BF7FC8D63F7FADAB000000003F800000
V2 : FE010000FE010000FE010000FE010000 FE010000FE010000FE010000FE010000
V4 : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 01000100010001000100010001000100
V6 : FF010100FF010100FF010100FF010100 FF010101FF010101FF010101FF010101
V8 : FF010101FF010101FF010101FF010101 FF010101FF010101FF010101FF010101
V10: 01010101010101010101010101010101 0405060708090A0B0C0D0E0F10111213
V12: FF010101FF010101FF010101FF010101 3FA052C0BFC465330000000000000000
V14: 001002120414061608180A1A0C1C0E1E 01000100010001000100010001000100
V16: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FF000000FF000000FF000000FF000000
V18: FE010000FE010000FE010000FE010000 00000000000000000000000000000000
V20: 00000000000000000000000000000000 00000000000000000000000000000000
V22: 00000000000000000000000000000000 00000000000000000000000000000000
V24: 00000000000000000000000000000000 00000000000000000000000000000000
V26: 01010101010101010101010101010101 00000102030304050606070809090A0B
V28: 04040506070708090A0A0B0C0D0D0E0F 0C0C0D0E0F0F10111212131415151617
V30: 1818191A1B1B1C1D1E1E1F0001010203 FF000000FF000000FF000000FF000000
VSCR: 00010000 VRSAVE: 00000000

Registers pointing to code:
r10: module kernel at 0x0181D87C (section 0 @ 0x1D880)



The adresses of crashes process different , so it happenes in different places of LodePaint as i understand. But error always the same:

DSI verbose error description: Access not found in hash or BAT (page fault)
Access was a store operation
Also it always pointed on r10: module kernel at 0x0181D87C (section 0 @ 0x1D880) at the end.
And Instruction pointer: in module kernel+0x00019F4C (0x01819F4C) always the same too.

The question is: How to fix it, and how to detect where bug is happenes, and did it bug in LodePaint, or in kernel, or anything else ..

Did that outputs show any address, which i can use for addr2line, to found where is bug in programm happenes ? I see only address related to kernel (like in module kernel+0x00019F4C).

Any ideas, suggestions and alt are welcome.


@RaserX
Can you please make lockup happenes, then reboot by 3buttons, and then type in console "dumpdebugbuffer" and put output here ?


Edited by kas1e on 2010/7/11 12:46:59
Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Need help to catch the bug of random lockups of LodePaint
Home away from home
Home away from home


See User information
Short update:

Trying to use debug version of kernel. The same lockups at random, and the same 1 address in kernel all the time and the same error:

Quote:


Dump of context at 0x020A91F0
Trap type: DSI exception
Machine State (raw): 0x0200F030
Machine State (verbose): [ExtInt on] [User] [FPU on] [IAT on] [DAT on]
Instruction pointer: in module kernel+0x0001FBE8 (0x0181FBE8)
Crashed process: lodepaint (0x65E70C40)
DSI verbose error description: Access not found in hash or BAT (page fault)
Access was a store operation
0: 63976FDC 62FB58C0 00000000 63976FDC 0200B6DC 00000000 00000020 0000006C
8: 00000001 BCFF6140 7FFFFFFD BCFF6140 24448048 630A5240 62FBEFFC 021C0000
16: 00000000 00000000 021C69A6 00000010 00000010 00001000 02090000 021C0000
24: 01856EB8 00000000 02090000 EFFFE910 02090000 01849678 639761C0 63976FDC
CR: 48428048 XER: 00000000 CTR: 0181FC4C LR: 0181FC9C
DSISR: 42000000 DAR: BCFF6144

... blablablabl. ....


Dump of context at 0xEFDAC3E0
Trap type: DSI exception
Machine State (raw): 0x0200F030
Machine State (verbose): [ExtInt on] [User] [FPU on] [IAT on] [DAT on]
Instruction pointer: in module kernel+0x0001FBE8 (0x0181FBE8)
Crashed process: lodepaint (0x65E70C40)
DSI verbose error description: Access not found in hash or BAT (page fault)
Access was a store operation
0: 63976FDC 62FB58C0 00000000 63976FDC 0200B6DC 00000000 00000020 0000006C
8: 00000001 BCFF6140 7FFFFFFD BCFF6140 24448048 630A5240 62FBEFFC 021C0000
16: 00000000 00000000 021C69A6 00000010 00000010 00001000 02090000 021C0000
24: 01856EB8 00000000 02090000 EFFFE910 02090000 01849678 639761C0 63976FDC
CR: 48428048 XER: 00000000 CTR: 0181FC4C LR: 0181FC9C
DSISR: 42000000 DAR: BCFF6144

... blablabl ...

Registers pointing to code:
r4 : module kernel at 0x0200B6DC (section 2 @ 0xB6E0)



With kernel.debug at any lockup addresses always:
Instruction pointer: in module kernel+0x0001FBE8 (0x0181FBE8)
r4 : module kernel at 0x0200B6DC (section 2 @ 0xB6E0)

So, i thinking that kernel.debug will show me some info maybe by addr2line, and i try found name of section 2 by readelf:
Quote:

5/0.RAM Disk:> readelf -S system:Kickstart/kernel

Section Headers:
[Nr] Name Type Addr Off Size ES Flg Lk Inf Al
[ 0] NULL 00000000 000000 000000 00 0 0 0
[ 1] .text PROGBITS 00000000 000040 08af8c 00 AX 0 0 16
[ 2] .rela.text RELA 00000000 11eb08 046b3c 0c 16 1 4
[ 3] .rodata PROGBITS 00000000 08afd0 0073b8 00 A 0 0 8
[ 4] .rela.rodata RELA 00000000 165644 008d6c 0c 16 3 4
... bablablab ...


I try by addr2line nextly:

Quote:


5/0.Work:lodepaint> addr2line -e system:Kickstart/kernel --section=.rela.text 1fbe8
addr2line: system:Kickstart/kernel: cannot find section .rela.text

5/1.Work:lodepaint> addr2line -e system:Kickstart/kernel --section=.text 1fbe8
??:0



So no luck for me to detect what happenes for now ..

Any ideas ? Anyone ?

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Need help to catch the bug of random lockups of LodePaint
Home away from home
Home away from home


See User information
By MemGuard+Sashimi, i found that one of the errors happenes exactly when you press "NEW"

Quote:


MEMGUARD HIT - [1] "lodepaint" (663b9d70)
rear wall damaged -- 63915570 = AllocVec(32, 00000000)
0: 00000000 6355d460 00000000 020a2bc8 63915570 6390bd20 5fa50068 00000004
8: 63590000 65bf0000 5fa5008c 7fb9c9c8 28422044 63595280 00000000 00000000
16: 645a46c0 7e5a0c9c 00000000 65b90420 02270000 00340014 02270000 66690000
24: 66690000 666a0000 00000001 00000001 63bf33d0 6390bd20 00000000 6390bd20
----> 020a2bc8 : "kernel" segment 0001 offset 42bc4
----> 63590000 : "lodepaint" segment 0005 offset 3fb8
----> 7fb9c9c8 : "work:debug/memguard/MemGuard" segment 0005 offset 89c0
----> 63595280 : "lodepaint" segment 0005 offset 9238
----> 7e5a0c9c : "lodepaint" segment 0004 offset 18ac94
----> 02270000 : "massstorage.usbfd" segment 0001 offset 077c
----> 02270000 : "massstorage.usbfd" segment 0001 offset 077c
----> 666a0000 : "LIBS:minigl.library" segment 0004 offset dfb8
LRa 7f53d3e4 : "LIBS:Warp3D/HWdrivers/W3D_R200.library" segment 0005 offset 53dc
CTRa 7fb9c950 : "work:debug/memguard/MemGuard" segment 0005 offset 8948
LR 7f53c4c0 : "LIBS:Warp3D/HWdrivers/W3D_R200.library" segment 0005 offset 44b8
CTR 7fb9c9c8 : "work:debug/memguard/MemGuard" segment 0005 offset 89c0

Stack backtrace:
----> 7f53c4c0 : "LIBS:Warp3D/HWdrivers/W3D_R200.library" segment 0005 offset 44b8
----> 7f556960 : "LIBS:Warp3D.library" segment 0005 offset 5958
----> 7f57989c : "LIBS:minigl.library" segment 0005 offset 17894
----> 7e6f2204 : "lodepaint" segment 0004 offset 2dc1fc
----> 7e73ecbc : "lodepaint" segment 0004 offset 328cb4
----> 7e73f2f8 : "lodepaint" segment 0004 offset 3292f0
----> 7e5db998 : "lodepaint" segment 0004 offset 1c5990
----> 7e59a3c4 : "lodepaint" segment 0004 offset 1843bc
----> 7e59e57c : "lodepaint" segment 0004 offset 188574
----> 7e5a0b98 : "lodepaint" segment 0004 offset 18ab90
----> 7e5a0d9c : "lodepaint" segment 0004 offset 18ad94
----> 01a3fea4 : "newlib.library.kmod" segment 0000 offset 1f40
----> 01a40af0 : "newlib.library.kmod" segment 0000 offset 2b8c
----> 01a40cb4 : "newlib.library.kmod" segment 0000 offset 2d50
----> 7e417b80 : "lodepaint" segment 0004 offset 1b78
----> 0191ce24 : "dos.library.kmod" segment 0000 offset 1b520
----> 0183ef08 : "kernel" segment 0000 offset 3ef04
----> 0183ef88 : "kernel" segment 0000 offset 3ef84



But i am not sure, that it can cause LockUp. Because if no GR spawned, then its not so important bug imho , which cant cause a lockups ? Imho that hit, only show that on some stage bad allocation of memory are happenes ? For me from that output are hardly to detect where problem starts , and what address use for addr2line. Can anybody help a bit ?


Edited by kas1e on 2010/7/11 15:36:11
Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Need help to catch the bug of random lockups of LodePaint
Home away from home
Home away from home


See User information
@kas1e
If high-tec analysis like this fails, you could try low-tech (and laborious) method of recompiling LodePaint with various parts of the program disabled, and seeing if you can find what is causing the problem... Ideally you end-up disabling everything except what is needed to cause the crash.

Author of the PortablE programming language.
Go to top
Re: Need help to catch the bug of random lockups of LodePaint
Home away from home
Home away from home


See User information
@ChrisH

That is worst-worst-worst solution for found the bug :) Did that MemGuard output have any info, which point on address where is crash happenes ?

Imho, that MemGuard hit show me the same info as GR do related to stack trace. If so, then, bug happenes in the w3d library in end, and coming from lodepaint, at segment 0004 offset 2dc1fc. Nope ?

Btw, just in interest: why GR show nothing, but MemGuard show that bug ? Bug imho pretty heavy, because if i not run MemGuard, and just trying many times do NEW, then lockup is coming. But GR in silence mode.

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Need help to catch the bug of random lockups of LodePaint
Home away from home
Home away from home


See User information
@CrhisH

Check this out, i just debug every address, just to see on which it point:

Quote:

Stack backtrace:
----> 7f53c4c0 : "LIBS:Warp3D/HWdrivers/W3D_R200.library" segment 0005 offset 44b8
----> 7f556960 : "LIBS:Warp3D.library" segment 0005 offset 5958
----> 7f57989c : "LIBS:minigl.library" segment 0005 offset 17894
----> 7f9192a4 : "lodepaint" segment 0004 offset 2dc29c
----> 7f965d5c : "lodepaint" segment 0004 offset 328d54
----> 7f966398 : "lodepaint" segment 0004 offset 329390
----> 7f802a38 : "lodepaint" segment 0004 offset 1c5a30
----> 7f7c1464 : "lodepaint" segment 0004 offset 18445c
----> 7f7c561c : "lodepaint" segment 0004 offset 188614
----> 7f7c7c38 : "lodepaint" segment 0004 offset 18ac30
----> 7f7c7e3c : "lodepaint" segment 0004 offset 18ae34
----> 01a3fea4 : "newlib.library.kmod" segment 0000 offset 1f40
----> 01a40af0 : "newlib.library.kmod" segment 0000 offset 2b8c
----> 01a40cb4 : "newlib.library.kmod" segment 0000 offset 2d50
----> 7f63eb80 : "lodepaint" segment 0004 offset 1b78
----> 0191ce24 : "dos.library.kmod" segment 0000 offset 1b520
----> 0183ef08 : "kernel" segment 0000 offset 3ef04


Quote:

9/0.Work:--SDL_PORTS/new9.!!!/a/lodepaint> addr2line -e lodepaint --section=.text 0x2dc29c
/SDK/local/common/include/mgl/minigl.h:718


That string mean:

MGLAPI void glTexCoord2d(GLdouble s, GLdouble t)
{
CC->GLTexCoord2f((GLfloat)s,(GLfloat)t);
}

So maybe its again realted of opengl context, which not present, and programm trying to create a new image with not presenting context.. And nextly:

Quote:

9/0.Work:--SDL_PORTS/new9.!!!/a/lodepaint> addr2line -e lodepaint --section=.text 0x328d54
/Work/--SDL_PORTS/new9.!!!/lodepaint/trunk/main_program/src/paint_window.cpp:571

9/0.Work:--SDL_PORTS/new9.!!!/a/lodepaint> addr2line -e lodepaint --section=.text 0x329390
/Work/--SDL_PORTS/new9.!!!/lodepaint/trunk/main_program/src/paint_window.cpp:625

9/0.Work:--SDL_PORTS/new9.!!!/a/lodepaint> addr2line -e lodepaint --section=.text 0x1c5a30
/Work/SDK/gcc/bin/../lib/gcc/ppc-amigaos/4.2.4/../../../../include/c++/4.2.4/bits/stl_vector.h:599

9/0.Work:--SDL_PORTS/new9.!!!/a/lodepaint> addr2line -e lodepaint --section=.text 0x18445c
/Work/--SDL_PORTS/new9.!!!/lodepaint/trunk/main_program/src/main.cpp:1369

9/0.Work:--SDL_PORTS/new9.!!!/a/lodepaint> addr2line -e lodepaint --section=.text 0x188614
/Work/--SDL_PORTS/new9.!!!/lodepaint/trunk/main_program/src/lpi/lpi_gui_base.h:166

9/0.Work:--SDL_PORTS/new9.!!!/a/lodepaint> addr2line -e lodepaint --section=.text 0x18ac30
/Work/SDK/gcc/bin/../lib/gcc/ppc-amigaos/4.2.4/../../../../include/c++/4.2.4/bits/stl_tree.h:198

9/0.Work:--SDL_PORTS/new9.!!!/a/lodepaint> addr2line -e lodepaint --section=.text 0x18ae34
/Work/--SDL_PORTS/new9.!!!/lodepaint/trunk/main_program/src/main.h:185

9/0.Work:--SDL_PORTS/new9.!!!/a/lodepaint> addr2line -e lodepaint --section=.text 1b78
/Work/--SDL_PORTS/new9.!!!/lodepaint/trunk/main_program/src/lpi/lodepng.cpp:4088


I write a message to main author, and he say that he will try to detect where is problem. I send him all that debug outputs and add2line strings, so, maybe it will helps.

The other interesting think, that with running MemGuard at background, i never have any lockup !

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Need help to catch the bug of random lockups of LodePaint
Not too shy to talk
Not too shy to talk


See User information
@kas1e

Sorry, it is very hard to help here because the DSI exception is caused by the kernel, it is not a direct access from the user application.

Did you look at the recent changes in the LodePaint code ? Maybe a problem is mentionned and fixed ? Maybe there is a problem with SDL.

Go to top
Re: Need help to catch the bug of random lockups of LodePaint
Just popping in
Just popping in


See User information
@kas1e

Quote:

@RaserX
Can you please make lockup happenes, then reboot by 3buttons, and then type in console "dumpdebugbuffer" and put output here ?

I'll try, but I don't think the "three fingered salute" works after my lockup.

'non fixed' A1XE, USB card, Sil 0680 IDE, 512mb RAM, Radeon 9250, OS4.1 Update 5
Go to top
Re: Need help to catch the bug of random lockups of LodePaint
Home away from home
Home away from home


See User information
@corto

Quote:

Sorry, it is very hard to help here because the DSI exception is caused by the kernel, it is not a direct access from the user application.


Are you sure that is by kernel ? Imho MemGuard hit show that is in LodePaint ?

Quote:

Did you look at the recent changes in the LodePaint code ? Maybe a problem is mentionned and fixed ? Maybe there is a problem with SDL.

Yeah, i have contact with author, and when he will fix it, he will write me mail. Last revision for moment are 94 (in last 3 days), but about bugs we talk with author yesterday first time.

For now he will try to fix all errors which he catch by ValGrind on linux. Strange think that ValGrind not show that "NEW/OK" hit which i have on aos4, but , show hit when he close image :) Anyway, let's wait a bit, firstly he will fix ValGrinds errors, then our NEW/OK hit, and then will see will be still here bugs or not ..

Related to SDL, i think more possible errors related to minigl/warp3d. Just because all DSIs and that HIT, not refering at all to SDL, but refering to lodepaint, minigl and w3d.

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Need help to catch the bug of random lockups of LodePaint
Just popping in
Just popping in


See User information
@RacerX

Quote:

RacerX wrote:
@kas1e

Quote:

@RaserX
Can you please make lockup happenes, then reboot by 3buttons, and then type in console "dumpdebugbuffer" and put output here ?

I'll try, but I don't think the "three fingered salute" works after my lockup.

Just tried again, 3 button reboot does not work. The only way I could reset it was to power off.

I suppose 'dumpdebugbuffer' is no good after turning the power off?

'non fixed' A1XE, USB card, Sil 0680 IDE, 512mb RAM, Radeon 9250, OS4.1 Update 5
Go to top
Re: Need help to catch the bug of random lockups of LodePaint
Home away from home
Home away from home


See User information
@RacerX

Quote:

I suppose 'dumpdebugbuffer' is no good after turning the power off?


Yep, in that way it will show nothing :( But le'ts wait a bit, i will compile new version today, and if bug will not fixed, we will try to use MemGuard + Shashimi on your config, to see, when problems start to happenes.

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top

  Register To Post

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project