Modify ↓
#337 closed bug (fixed)Read tab in config DISs
DescriptionSummary
READ in config shows a DSI crashlog Steps to reproduce
Expected results
See read options/windows Actual results
Shows a GR with a DSI error Regression
Sorry for not entering, can't log from muiOWB, and I can't remember my usr/psw. Can someone reset/delte them. NotesAttachments (9)Change History (23)Changed 10 months ago by anonymouscomment:1 Changed 10 months ago by thboeckel
First and most important rule: if you see the GrimReaper then PLEASE provide the crashlog. Without it your bug report is of not much worth. comment:2 Changed 10 months ago by thboeckel
I just tried the latest nightly build (17.7.2012) myself and for me there is no crash happening when switching to the Read page of YAM's config. comment:3 Changed 10 months ago by damato
Sorry, but I am also not able to reproduce your crashes. Please understand that crashlogs alone doesn't help at all times. So please download a debug version of the latest YAM nightly (http://yam.ch/download/nightly/YAM28dev-AmigaOS4-debug.lha) and execute the following command in a shell before starting YAM: setenv yamdebug config file:ram:yam.log
Then run the debug version as usual and try to get the crash again. Afterwards, please review the file RAM:yam.log and remove all private information. Then upload the logfile here so that we can review it.
For more information on debugging YAM please read http://yam.ch/wiki/FAQ/Debugging#BasicsaboutYAMsdebuggingfacilities comment:4 Changed 10 months ago by damato
Sorry, but the yam.log file didn't help a lot, please redo it using the following setenv call: setenv yamdebug @all all
Be prepared that it will get pretty large. In addition, please do not proceed in the GrimReaper. So please do not press Contiune or Abort in the grim reaper so that YAM continues. Right when the crash happens copy the yam.log to a safe directory and then attach it again to this ticket. comment:5 Changed 10 months ago by javierdlr
About the new yam.debug. When i get the GR windows if I don't click on CONTINUA or IGNORE DSIs debug output stops at: .. (0x698BD900) module Kickstart/intuition.library.kmod at 0x0158FA24 (section 0 @ 0x8428) (0x698BD910) module Kickstart/intuition.library.kmod at 0x0158F664 (section 0 @ 0x8068) (0x698BD980) YAM.debug:main()+0x26FC (section 1 @ 0xB08C) (0x698BDD00) module Kickstart/newlib.library.kmod at 0x017AF1AC (section 0 @ 0x2090) (0x698BDD70) module Kickstart/newlib.library.kmod at 0x017AFE0C (section 0 @ 0x2CF0) (0x698BDF10) module Kickstart/newlib.library.kmod at 0x017AFFD0 (section 0 @ 0x2EB4) (0x698BDF50) YAM.debug:_start()+0x170 (section 1 @ 0x170) (0x698BDF90) module Kickstart/dos.library.kmod at 0x014F1B54 (section 0 @ 0x22858) (0x698BDFC0) module Kickstart/kernel at 0x01441748 (section 0 @ 0x4174C) (0x698BDFD0) module Kickstart/kernel at 0x014417C8 (section 0 @ 0x417CC) (0x698BDFE0) Disassembly of crash site: 017D7778: 3565FFFF subic. r11,r5,1 017D777C: 7C090378 mr r9,r0 017D7780: 41820028 beq- 0x17D77A8 017D7784: 7D6903A6 mtctr r11 >017D7788: 88030000 lbz r0,0(r3) 017D778C: 38630001 addi r3,r3,1 017D7790: 2F800000 cmpwi cr7,r0,0 017D7794: 98090000 stb r0,0(r9) 017D7798: 39290001 addi r9,r9,1 017D779C: 419E0030 beq- cr7,0x17D77CC Stack pointer (0x698BBCE0) is inside bounds Redzone is OK (4) 68k register dump DATA: 6C09A1FE 00000003 00000000 00000000 00000000 00000000 00000000 00000000 ADDR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 698BCED0 Page information: Page not found
NO MORE OUTPUT IT JUST STOPS HERE!!!!!! comment:6 Changed 10 months ago by damato
Ok thanks for the debug output. However, please find attached a new YAM debug version. Please download, install and then run the following setenv command before running it: setenv yamdebug config file:ram:yam.log
Then run YAM and try to get the crash again. Right when the crash happens don't press any button in grim reaper and simply upload the new yam.log file as it is. comment:7 Changed 10 months ago by javierdlr
Done, attached YAM.os4 debug log (getting GR, not clicking on CONTNINUE/IGNORE_DSI,..) OUPS, sorry systems freezed. 2nd file attached is the one a I get with 'setenv yamdebug config file:ram:yam.log'.
To be more precisenly it stops in yam.log:
Tested 2 times and it stopped/crashes here at same place. comment:8 Changed 10 months ago by damato
Sorry, but you did it again wrong. As I said, DO NOT continue with grim reaper at all. That means, do the following
Its so easy, but yet you seem to make always the same mistake: you always press a button in grim reaper before you catched all debug output. comment:9 Changed 10 months ago by javierdlr
Ok, sorry for beeing soo stupid
[CLI 2]
Version 0, edited 10 months ago
by javierdlr
(next)
comment:10 Changed 10 months ago by damato
Ok. getting better. However, please run YAM again with the new version I am going to upload next. And also please do not post the logfile here inline but always upload the file via the "attach" functionality of this ticket system.
So please run the test again with the same setenv call and send the new yam.log ASAP. comment:11 Changed 10 months ago by javierdlr
Done, attached is new yan.log with YAM.os4 (3005616 bytes)
and with the latest nighly build debug .. 00:D: YAM.c:525:initialised ADST notify request on file 'ENV:TZONE' 00:D:YAM.c:2826:YAM allocated signals: 00:D:YAM.c:2827: adstsig = 00080000 00:D:YAM.c:2828: timsig = 02000000 00:D:YAM.c:2829: rexxsig = 00100000 00:D:YAM.c:2830: appsig = 01000000 00:D:YAM.c:2831: applibsig = 00400000 00:D:YAM.c:2832: writeWinNotifySig = 00800000 00:D:YAM.c:2833: threadsig = 80000000 00:D:YAM.c:2834: methodStackSig = 40000000 00:W: Timer.c:240:timer[5]: already stopped 00:C: YAM_CO.c:1878:sco = 1785602352, 0x6a6e2130 00:C: YAM_CO.c:1879:dco = 1770184720, 0x6982e010 00:W: YAM_UT.c:1794:potential invalid ObtainDirContextTags call with return (0x00000000, 0x00000001) 00:W: FilterChooser.c:204:potential invalid ObtainDirContextTags call with return (0x00000000, 0x00000001) comment:12 Changed 10 months ago by thboeckel
comment:13 Changed 10 months ago by damato
As you can see, Thore fixed the problem now. Please wait until a new nightly build is generated the next night and then test again if the problem is really fixed. If the problem still exists please reopen this ticket. comment:14 Changed 10 months ago by javierdlr
Tested with latest dev YAM 2.8-dev (20-07-2012)
GREAT WORK!!! THX Note: See
TracTickets for help on using
tickets. | This list contains all users that will be notified about changes made to this ticket. These roles will be notified: Reporter, Owner, Subscriber
| ||||||||||||||||||||||||||||



crashlog