Can't hit a breakpoint in CETK source

I am trying to debug a GDI CETK failure, but I cannot hit a breakpoint in
some source code (I have the shared source installed) that I know is being
executed. I believe this is a problem with the Source Path Mapping, but my
efforts to fix it have fallen short so far.

I looked into the gdiapi.pdb and ddi_test.pdb files and found references to
files in the following directories:
C:\ymzki\
C:\yzqa\
C:\yzqasp1\

Using the Source Path Mapping tool in PB, I mapped these paths to my Wince
root, which is F:\WCE6\WINCE600. Still, I cannot get a breakpoint to hit, or
even to show up as a full red circle (I get the unrecognized empty red circle
instead).

Any pointers on getting a CETK source code breakpoint recognized? Am I
missing anything here?

Thanks,
Danny

Bruce
Wed Mar 19 09:54:22 PDT 2008

Are you running from ROM? You probably need to move ceddk.dll to the files
section of the bib file or compress it or leave it out of the nk and load it
from the \Release folder.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"Danny" <Danny@discussions.microsoft.com> wrote in message
news:E0824AA6-0EC7-4C92-97E7-41FF4C0DEB3C@microsoft.com...
>I am trying to debug a GDI CETK failure, but I cannot hit a breakpoint in
> some source code (I have the shared source installed) that I know is being
> executed. I believe this is a problem with the Source Path Mapping, but
> my
> efforts to fix it have fallen short so far.
>
> I looked into the gdiapi.pdb and ddi_test.pdb files and found references
> to
> files in the following directories:
> C:\ymzki\
> C:\yzqa\
> C:\yzqasp1\
>
> Using the Source Path Mapping tool in PB, I mapped these paths to my Wince
> root, which is F:\WCE6\WINCE600. Still, I cannot get a breakpoint to hit,
> or
> even to show up as a full red circle (I get the unrecognized empty red
> circle
> instead).
>
> Any pointers on getting a CETK source code breakpoint recognized? Am I
> missing anything here?
>
> Thanks,
> Danny

Danny
Mon Mar 24 12:10:04 PDT 2008

Bruce,

I am running from RAM, so that is not the issue.

I am finally getting my breakpoints recognized, and I'm not exactly sure
which change I made to get it to work. I think it may be that once I made
the changes to the Source Path Mapping, that I needed to rebuild my image, or
at least reconnect with KITL.

Thanks for the prompt response,
Danny

"Bruce Eitman [eMVP]" wrote:

> Are you running from ROM? You probably need to move ceddk.dll to the files
> section of the bib file or compress it or leave it out of the nk and load it
> from the \Release folder.
>
> --
> Bruce Eitman (eMVP)
> Senior Engineer
> beitman AT applieddata DOT net
>
> Applied Data Systems
> www.applieddata.net
> An ISO 9001:2000 Registered Company
> Microsoft WEP Gold-level Member
>
> "Danny" <Danny@discussions.microsoft.com> wrote in message
> news:E0824AA6-0EC7-4C92-97E7-41FF4C0DEB3C@microsoft.com...
> >I am trying to debug a GDI CETK failure, but I cannot hit a breakpoint in
> > some source code (I have the shared source installed) that I know is being
> > executed. I believe this is a problem with the Source Path Mapping, but
> > my
> > efforts to fix it have fallen short so far.
> >
> > I looked into the gdiapi.pdb and ddi_test.pdb files and found references
> > to
> > files in the following directories:
> > C:\ymzki\
> > C:\yzqa\
> > C:\yzqasp1\
> >
> > Using the Source Path Mapping tool in PB, I mapped these paths to my Wince
> > root, which is F:\WCE6\WINCE600. Still, I cannot get a breakpoint to hit,
> > or
> > even to show up as a full red circle (I get the unrecognized empty red
> > circle
> > instead).
> >
> > Any pointers on getting a CETK source code breakpoint recognized? Am I
> > missing anything here?
> >
> > Thanks,
> > Danny
>
>
>