Help with debug options
  • Order of the Butterfly
    Order of the Butterfly
    Framiga
    Posts: 363 from 2003/7/11
    From: Milan-Italy
    Hi all

    i need a help from someone using MOS for PowerUP and MUI4 with YAM2.5dev (or others MUI apps but IBrowse)

    I get this MUI4 debug output in Sashimi (serial out), every time i iconify/de-iconify and quit YAM2.5dev:

    Sashimi installed ([Ctrl]+C or "Break 5" to remove)
    0000000000000000MUIP_AskMinMax: bogus: min=-1/15 def=-1/15 max=10060/15 for obj=0x0988b2f0(0)(Group.mui)In Arrivo
    0000000000000000MUIP_AskMinMax: bogus: min=-1/19 def=-1/19 max=10000/19 for obj=0x0987f3e8(0)(Group.mui)
    00000000000000000MUI_LayoutObj: obj=0x09881498(0)(Image.mui)0x0 10166/10367 8x8 failed completely (min=0x0 max=0x0)
    00000000000000000MUI_LayoutObj: obj=0x0989aba0(0)(Image.mui)0x0 10761/10367 8x8 failed completely (min=0x0 max=0x0)
    00000000000000MUIP_ShowClipped: obj=0x09881498(0)(Image.mui)0x0 <- no previous MUIM_Layout
    00000000000000MUIP_ShowClipped: obj=0x0989aba0(0)(Image.mui)0x0 <- no previous MUIM_Layout
    00000000000000000MUI_LayoutObj: obj=0x09881498(0)(Image.mui)0x0 10166/10367 8x8 failed completely (min=0x0 max=0x0)
    00000000000000MUIP_ShowClipped: obj=0x09881498(0)(Image.mui)0x0 <- no previous MUIM_Layout
    00000000000000000MUI_LayoutObj: obj=0x0989aba0(0)(Image.mui)0x0 10761/10367 8x8 failed completely (min=0x0 max=0x0)
    00000000000000MUIP_ShowClipped: obj=0x0989aba0(0)(Image.mui)0x0 <- no previous MUIM_Layout
    00000000000000000MUI_LayoutObj: obj=0x09881498(0)(Image.mui)0x0 10166/10367 8x8 failed completely (min=0x0 max=0x0)
    00000000000000000MUI_LayoutObj: obj=0x09881498(0)(Image.mui)0x0 10166/10367 8x8 failed completely (min=0x0 max=0x0)
    00000000000000000MUI_LayoutObj: obj=0x09881498(0)(Image.mui)0x0 10166/10367 8x8 failed completely (min=0x0 max=0x0)
    00000000000000000MUI_LayoutObj: obj=0x09881498(0)(Image.mui)0x0 10166/10367 8x8 failed completely (min=0x0 max=0x0)

    can you confirm this? and if NOT, what are your debug options in SYS:Startup-Sequence?

    My goal would be to redirect all this otput in ramdebug, because WITHOUT sashimi running, YAM takes 4-5 seconds to iconify/deiconify/quitting.

    All these on MOS for PowerUP only.

    Thanks.
  • »05.08.07 - 14:49
    Profile
  • Order of the Butterfly
    Order of the Butterfly
    Framiga
    Posts: 363 from 2003/7/11
    From: Milan-Italy
    hugh! am i asking to much?
  • »07.08.07 - 10:29
    Profile
  • MorphOS Developer
    jacadcaps
    Posts: 1939 from 2003/3/5
    From: Canada
    Well... are you sure you have ramdebug enabled? kprintfs should go to ramdebug by default afair.
  • »07.08.07 - 11:36
    Profile Visit Website
  • Acolyte of the Butterfly
    Acolyte of the Butterfly
    Amigaz
    Posts: 121 from 2005/6/11
    Quote:


    Framiga wrote:
    hugh! am i asking to much?




    I could have gave you some info if I had my A4000 hooked up :(
    If you can wait until the end of the week I give you the debug info from my A4000
    Have my Peg II hooked up at the moment and I haven't got enough time in the evenings right now to fiddle to much with my computers :(
    --------------------------------------------------------------
    MorphOS PowerUP powered Amiga 4000
    --------------------------------------------------------------
    Pegasos II G4 1ghz
    Radeon 8500 128mb
    Soundblaster Live 5.1 Digital
    Realtek 2139B 100mbit
  • »07.08.07 - 11:38
    Profile
  • Order of the Butterfly
    Order of the Butterfly
    Framiga
    Posts: 363 from 2003/7/11
    From: Milan-Italy
    hello jacadcaps

    here my startup line:

    cd sys:boot
    startup hal=roms/hal.com1 kernel=roms/kernel.com1 abox=roms/abox2.com1 module=roms/module.com1 resetlevel=$resetlevel ramdebug EDebugFlags="NoLogServer LoadSeg" sumkick disableled delay=$delay extmodules=extmodules/#? $bootdevice $kickstart >NIL:

    but even changing some EDebugFlags=, doesn't redirect that MUI4 debug/warning ro ramdebug
  • »07.08.07 - 11:50
    Profile
  • Order of the Butterfly
    Order of the Butterfly
    Framiga
    Posts: 363 from 2003/7/11
    From: Milan-Italy
    Thanks anyway AMIGAZ! ... this issue seems more annoying of what i thought! :-)
  • »07.08.07 - 11:51
    Profile
  • Order of the Butterfly
    Order of the Butterfly
    Framiga
    Posts: 363 from 2003/7/11
    From: Milan-Italy
    @jacadcaps

    tried also with:

    EDebugFlags="NoLogServer logkprintf"

    EDebugFlags="Logkprintf"

    EDebugFlags=""

    same output redirected to serial (sashimi)
  • »07.08.07 - 12:00
    Profile
  • Order of the Butterfly
    Order of the Butterfly
    Framiga
    Posts: 363 from 2003/7/11
    From: Milan-Italy
    ok ... i'll reply to myself (not a good sign at all but, hey ... for the good of my beloved "commmmunity")..

    This issue seems affect PowerUP system only (or goes not noticed on Ghz machines)

    anyway is enough to slap LogTool (configured in serial port mode out) in WBStartup and the slowsdown go away (thanks to LogTool that open it)

    This is probably because the serial.device in NOT opened/used on my system

    Anyway .... fixed now!

    edit- ah ... switched definitively on Ambient/MUI4 now!

    MUI4 WIP



    [ Edited by Framiga on 2007/8/9 10:59 ]
  • »09.08.07 - 10:48
    Profile