From: Peter De Lucia <peter_at_dualice.net>
Date: Wed, 5 Feb 2003 13:33:19 -0500 (EST)

I'm not having those types of problems. I am just trying to figure out how
the code works and how to debug it.. I have put DEBUGF statements the
button.c and when I rebuilt and ran in the simulator I didn't see anything
coming out to stderr... I have to play some more
>
> 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.
>> >>
>> >>
>> >>
>>
>>
>>
>>
Received on 2003-02-05