Hi all,
Before starting a debug session, I’ve downloaded symbols from microsoft symbol server and with setting Debug info to Program Database option in Vc6, I could generate a pdb file and also setting symbol path in WinDbg, but when I want to set a break point a message box appears and tells that symbols for current line could not found and the breakpoint could not be set.
What can I do to set a breakpoint?
Thanks
Alireza
Hello,
is the specific module already loaded? Check out Debug -> Modules the check. In the “Symbol file” column there should be the PDB file (private) been displayed.
GP
xxxxx@BasamadCo.commailto:xxxxx wrote:
> Hi all,
> Before starting a debug session, I’ve downloaded symbols from
> microsoft symbol server and with setting Debug info to Program
> Database option in Vc6, I could generate a pdb file and also setting
> symbol path in WinDbg, but when I want to set a break point a
> message box appears and tells that symbols for current line could not
> found and the breakpoint could not be set. What can I do to set a
> breakpoint?
> Thanks
> Alireza</mailto:xxxxx>
Hallo g?nter,
thank you for answer.
The moudle has been loaded but in symbol column displays None.
Alireza
Hi g?nter,
in the symbol file column displays Bm.sys that is image name and not my pdb file name.
I do know why.
thanks
Alireza
hi alireza,
this is common, in debug window it displays dll and sys files , your pdb path will be set under
file –> symbol path –> symbol folder path.
Hi sainath,
symbol path has been already set for specified pdb file
Try:
!sym noisy
.reload /f bm.sys
That will show you where WinDBG is looking for your PDB and why it’s not
liking the one that it finds.
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
wrote in message news:xxxxx@windbg…
> Hi sainath,
>
> symbol path has been already set for specified pdb file
>
>
try using symstore utility to import .pdb to your symbols directory( say
c:\symbols)…it stores the pdb in some folder say bm.pdb(if thats the name
of your pdb)…inside that it creates a folder named with some guid…thats
where windbg mostly searched for pdb…u still need to give the symbol path
as the c:\symbols…
-nitesh
On Tue, Sep 22, 2009 at 7:05 PM, Scott Noone wrote:
> Try:
>
> !sym noisy
> .reload /f bm.sys
>
> That will show you where WinDBG is looking for your PDB and why it’s not
> liking the one that it finds.
>
> -scott
>
> –
> Scott Noone
> Consulting Associate
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
> wrote in message news:xxxxx@windbg…
> > Hi sainath,
> >
> > symbol path has been already set for specified pdb file
> >
> >
>
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>