Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide



Rockbox mail archive

Subject: Re: backlight issue
From: rockbox_at_diffenbach.org
Date: 2003-02-05


Ahem.
When I run the Win32 simulator build, I have problems with not being able to exit certain screens, which is why I'm logging actions in the button.c code. You're not by chnaced having similar problems, are you?

Quoting Peter De Lucia <peter_at_dualice.net>:

> Hmm.. thanks.. I guess I should have mentioned that I am runningit on
> linux.. maybe they go stderr??? If that is true.. I put DEBUGF
> statements
> in the button.c code and the backlight_on() function and nothing got
> printed out... I'll play somemore..
>
> Peter.
>
>
> >
> >> 2. If you put DEBUGF statements in the code, where do they show up?
> >> (on
> >> the JB and in the simulator)
> >
> > On the JB, I dunno. On the /MS Windows/ simulator, it ends up with a
> > call to OutputDebugString, a MS Windows API call that sends it to an
> > attached debugger.
> >
> > Quoting Peter De Lucia <peter_at_dualice.net>:
> >
> >> Hello,
> >>
> >> I thought I'd look into the
> >> backlight-coming-on-only-when-the-disk-spins
> >> issue. I was playing around with the code and added some lines to
> >> button.c
> >> (it looked like this is the place when user input is taken - if it
> >> isn't
> >> please let me know) to called the backlight_on function. I then
> built
> >> and
> >> copied the new version to my FM JB and tried it out. I didn't
> notice
> >> anything at all change.. I guess I have two questions,
> >>
> >> 1. How do you debug ?
> >> 2. If you put DEBUGF statements in the code, where do they show up?
> >> (on
> >> the JB and in the simulator)
> >>
> >> Thanks,
> >> Peter.
> >>
> >>
> >>
>
>
>
>



Page was last modified "Jan 10 2012" The Rockbox Crew
aaa