unable to reliably set break point in source code

WINDBG
1

I have a serial connection with the target machine and am using windbg
6.2.0007.4.

I have a source file open and am trying to set a break point and I get a
message back “symbol information for the current line could not be located
in the currently loaded symbols…”

The symbol path is correct and am able to set a break point with this
method occasionally. (It seems that I must reboot the target each time I
update the driver - even though I am disabling and reenabling the driver
from the control panel after I copy it, and copying the pdb file into my
symbols direcotry.)

Once I reboot the target, I can get it to work on the first time , but
after that I have difficulty getting this feature to work again.

What is the correct method of repeatedly (after a new driver isntall)
setting a break point from source level window?

Thanks

2

Before setting the break point try to unload the symbols and reload it.
.reload /u xxx.sys // to unload
.reload xxx.sys // to load the symbols.

-Srin.

-----Original Message-----
From: xxxxx@mail.com [mailto:xxxxx@mail.com]
Sent: Monday, June 16, 2003 10:05 AM
To: Kernel Debugging Interest List
Subject: [windbg] unable to reliably set break point in source code

I have a serial connection with the target machine and am using windbg
6.2.0007.4.

I have a source file open and am trying to set a break point and I get
a
message back “symbol information for the current line could not be
located
in the currently loaded symbols…”

The symbol path is correct and am able to set a break point with this
method occasionally. (It seems that I must reboot the target each time
I
update the driver - even though I am disabling and reenabling the
driver
from the control panel after I copy it, and copying the pdb file into
my
symbols direcotry.)

Once I reboot the target, I can get it to work on the first time , but
after that I have difficulty getting this feature to work again.

What is the correct method of repeatedly (after a new driver isntall)
setting a break point from source level window?

Thanks

You are currently subscribed to windbg as: xxxxx@nai.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

I routinely update the driver on the target machine by first ensuring no
exe has an open connection to the driver, and then disabling the driver
via Device Manager prior to copying over the new driver from my host
system. If there’s an exe with an open connection, XP replies with a
message to the effect of… “… you must reboot prior to this hardware
change taking effect…”

Even if I forget to kill the exe, I’m still ok. Simply dismiss the XP
message given above, then kill the exe with the open connection, and then
reenable, followed by another disable//enable. You’ll get another " you
must reboot…" type message after the reenable, but just dismiss it and
continue with the following disable//enable.

> I have a serial connection with the target machine and am using windbg
> 6.2.0007.4.
>
> I have a source file open and am trying to set a break point and I get a
> message back “symbol information for the current line could not be located
> in the currently loaded symbols…”
>
> The symbol path is correct and am able to set a break point with this
> method occasionally. (It seems that I must reboot the target each time I
> update the driver - even though I am disabling and reenabling the driver
> from the control panel after I copy it, and copying the pdb file into my
> symbols direcotry.)
>
> Once I reboot the target, I can get it to work on the first time , but
> after that I have difficulty getting this feature to work again.
>
> What is the correct method of repeatedly (after a new driver isntall)
> setting a break point from source level window?
>
> Thanks