Re: How does one report errors in common code to the WinCE team?
- From: William Powell <WilliamPowell@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 21 Jul 2008 13:28:21 -0700
Is there a way to determine whether you got charged for the incident or a way
to tell how many incidents you have left?
"Chris Tacke, eMVP" wrote:
As Paul pointed out, you get *free* incidents with PB, so I can't see how.
there's any risk of getting charged. There's a risk you might use up an
incident, but that's only if it turns out to not be a bug.
--
Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com
"William Powell" <WilliamPowell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0E4DB277-8FE6-4583-902A-67BD75C8B935@xxxxxxxxxxxxxxxx
Seems like a difficult procedure to do the e-mail support incidents (where
you have to risk getting charged $99 in order to suggest an improvement or
correction to the code). Also, when I went to the site, it would only
allow
me to enter a support request against WinCE 5.0. I saw no option for
winCE
6.0 R2.
The site was:
http://support.microsoft.com/ph/3100/en-us/ , then select contact support
pro by e-mail...
which put you at:
https://support.microsoft.com/oas/default.aspx?gprid=3100
which appears to be a site for WinCE 5.0 support. Trying the select a
product button showed only WinCE 5.0, no 6.0 option.
So, how do we get MS Embedded to create a way for developers to help
improve
the code without risking $$$ to do so? Seems like very, very few people
will
be providing improvements using the current process.
Thoughts?
"Paul G. Tobey [eMVP]" wrote:
The most-reliable way would be to start an email support incident, via
www.microsoft.com/embedded (navigate down through Windows CE, etc., to
find
the right starting point). Since you get a couple of support incidents
with
your PB purchase, you should have no problem with them wanting to charge
you
and, since it's clearly a bug, you shouldn't even lose the incident you
use.
Paul T.
"William Powell" <WilliamPowell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:F19D3050-66BE-4668-9923-A39EC3B45903@xxxxxxxxxxxxxxxx
In working with the KITLOutputDebugString() function to print Eboot
messages,
I think I found an error in the code. This function is in the
PLATFORM/COMMON/SRC/COMMON/BOOT/BLCOMMON/format.c file.
In this file, the variable szSprintf is not initialized. Although not
used
directly by KITLOutputDebugString (...), it is used by the
pOutputByte()
function, which is shared by KITLOutputDebugString() and
FormatString().
Problem:
On the first call to KITLOutputDebugString() and the first call to
pOutputByte, if the szSprintf value is not 0, the pOutputByte function
will
probably cause a memory exception when executing line 247:
*szSprintf++ = c;
Fix:
Initialize szSprintf to 0 within KITLOutputDebugString()
Current lines:
void KITLOutputDebugString (LPCSTR sz, ...)
{
unsigned char c;
va_list vl;
va_start(vl, sz);
while (*sz) {
c = *sz++;
...
Corrected lines:
void KITLOutputDebugString (LPCSTR sz, ...)
{
unsigned char c;
va_list vl;
va_start(vl, sz);
// ensure output goes to OEMWriteDebugByte
szSprintf = 0;
while (*sz) {
c = *sz++;
...
What's the best way to report this type of error?
- References:
- Re: How does one report errors in common code to the WinCE team?
- From: Paul G. Tobey [eMVP]
- Re: How does one report errors in common code to the WinCE team?
- From: William Powell
- Re: How does one report errors in common code to the WinCE team?
- From: Chris Tacke, eMVP
- Re: How does one report errors in common code to the WinCE team?
- Prev by Date: Re: How does one report errors in common code to the WinCE team?
- Next by Date: Re: CE 6.0 Networking Problems
- Previous by thread: Re: How does one report errors in common code to the WinCE team?
- Next by thread: Re: How does one report errors in common code to the WinCE team?
- Index(es):
Relevant Pages
|
