A small issue

WINDBG
1

Hi All,

I am doubtful about one thing,

what does 1e7 signify in the following.

Probably caused by : filespy.sys ( filespy!SpyCreate+1e7 )

Please Help.

Regards

Lalit.

2

It might be a local variable in function SpyCreate.

filespy!SpyCreate+1e7 => represents in filespy, it is referring the
symbol located at SpyCreate + 1e7 i.e. adding 1e7 to the address of
SpyCreate symbol.

If you take the symbols output of your exe you can locate the
variable. In Windows .map file will do i suppose. I am not sure.

-Rmsh.
“Lalit S. Rana” wrote:

Hi All,

I am doubtful about one thing,

what does 1e7 signify in the following.

Probably caused by : filespy.sys ( filespy!SpyCreate+1e7 )

Please Help.

Regards

Lalit.

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

–
http://voip.hcltech.com

3

If I’m right … In filespy.sys, offset 1e7 from/in function SpyCreate.

Rajiv.

-----Original Message-----
From: Lalit S. Rana [mailto:xxxxx@epatra.com]
Sent: Monday, June 09, 2003 2:19 PM
To: Kernel Debugging Interest List
Subject: [windbg] A small issue

Hi All,

I am doubtful about one thing,

what does 1e7 signify in the following.

Probably caused by : filespy.sys ( filespy!SpyCreate+1e7 )

Please Help.

Regards

Lalit.

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

4

:slight_smile:
This was hexadecimal offset 1e7 (487 decimal). It wasn’t the float.

Best Regards,
Timur

----- Original Message -----
From: “Lalit S. Rana”
Newsgroups: windbg
To: “Kernel Debugging Interest List”
Sent: Monday, June 09, 2003 12:48 PM
Subject: [windbg] A small issue

: Hi All,
:
: I am doubtful about one thing,
:
: what does 1e7 signify in the following.
:
: Probably caused by : filespy.sys ( filespy!SpyCreate+1e7 )
:
: Please Help.
:
: Regards
:
: Lalit.
:
:
:

5

Hi all,
I am a newbie in Kernel mode debugging and I could really use some simple advice…
I am trying to debug a kernel mode driver using two PC’s in a null modem cable connection.
The target system is running windows 2000 checked build and is has loaded the driver.
The Host system is running windows 2000 free build and WinDbg 6.2.0007.4.
I am trying to start debugging but I have not made it so far…
Here is what I am doing:
I have configured my target system to start in debug mode by adding the / debug/ debugport= com1 and 9600 baudrate in bmy boot.ini file in my target system.
When the target loads Win2000 I open windbg in my host system. I am enabling kernel mode debugging in Com2 at 9600 baudrate
windbg shows a message in the connect window “opened \. \com2 waiting to reconnect” while in the status bar
there is a "debuggee not connected " message.
What am I doing wrong??
Can someone give me some simple instructions on how to start my first debugging session?
( connect host and target, set my first breakpoint etc?)

Thank you all in advance.

panayiota

6

In your case if I were you I would make sure the following.

  1. connected the null modem cable to com2 (not com1.) I am not sure
    why you were using com2 on host instead of com1.
  2. on your target you said you added / debug/ debugport= com1.
    Spaces are located at wrong places. I am not sure if this causes the
    problem. I would correct to following /debug /debugport=com1
    /baudrate=115200
  3. Start the debugger on host.
  4. Restart the target and select Debugger Enabled option while
    booting.
  5. After a few seconds you should see some messages in your
    debugger.

-Srin.

-----Original Message-----
From: Panayiota Bay [mailto:xxxxx@athens.atmel.com]
Sent: Monday, June 09, 2003 3:37 AM
To: Kernel Debugging Interest List
Subject: [windbg] Re: A small issue

Hi all,

I am a newbie in Kernel mode debugging and I could really use some
simple advice…

I am trying to debug a kernel mode driver using two PC’s in a null modem
cable connection.

The target system is running windows 2000 checked build and is has
loaded the driver.

The Host system is running windows 2000 free build and WinDbg
6.2.0007.4.

I am trying to start debugging but I have not made it so far…

Here is what I am doing:

I have configured my target system to start in debug mode by adding the
/ debug/ debugport= com1 and 9600 baudrate in bmy boot.ini file in my
target system.

When the target loads Win2000 I open windbg in my host system. I am
enabling kernel mode debugging in Com2 at 9600 baudrate

windbg shows a message in the connect window “opened \. \com2 waiting
to reconnect” while in the status bar

there is a "debuggee not connected " message.

What am I doing wrong??

Can someone give me some simple instructions on how to start my first
debugging session?

( connect host and target, set my first breakpoint etc?)

Thank you all in advance.

panayiota

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

7

Thank you all, it appears that the COM port in the target was suffering a conflict issue.
I ve uninstalled com port reinstalled it again and not it works…
Thanks again for helping.

Panayiota
*************************************************
+++++++++++++++++++++++++++++++++
Panayiota Bay
Software Engineer, PSLI CAD Group
ATMEL HELLAS S.A
Multimedia and Communications
Tel:+30-210-9859621
Fax: +30-210-9859622
+++++++++++++++++++++++++++++++++
*************************************************
----- Original Message -----
From: xxxxx@NAI.com
To: Kernel Debugging Interest List
Sent: Monday, June 09, 2003 6:40 PM
Subject: [windbg] Re: A small issue

In your case if I were you I would make sure the following.

1… connected the null modem cable to com2 (not com1.) I am not sure why you were using com2 on host instead of com1.
2… on your target you said you added / debug/ debugport= com1. Spaces are located at wrong places. I am not sure if this causes the problem. I would correct to following /debug /debugport=com1 /baudrate=115200
3… Start the debugger on host.
4… Restart the target and select Debugger Enabled option while booting.
5… After a few seconds you should see some messages in your debugger.

-Srin.

-----Original Message-----
From: Panayiota Bay [mailto:xxxxx@athens.atmel.com]
Sent: Monday, June 09, 2003 3:37 AM
To: Kernel Debugging Interest List
Subject: [windbg] Re: A small issue

Hi all,

I am a newbie in Kernel mode debugging and I could really use some simple advice…

I am trying to debug a kernel mode driver using two PC’s in a null modem cable connection.

The target system is running windows 2000 checked build and is has loaded the driver.

The Host system is running windows 2000 free build and WinDbg 6.2.0007.4.

I am trying to start debugging but I have not made it so far…

Here is what I am doing:

I have configured my target system to start in debug mode by adding the / debug/ debugport= com1 and 9600 baudrate in bmy boot.ini file in my target system.

When the target loads Win2000 I open windbg in my host system. I am enabling kernel mode debugging in Com2 at 9600 baudrate

windbg shows a message in the connect window “opened \. \com2 waiting to reconnect” while in the status bar

there is a "debuggee not connected " message.

What am I doing wrong??

Can someone give me some simple instructions on how to start my first debugging session?

( connect host and target, set my first breakpoint etc?)

Thank you all in advance.

panayiota

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

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