Each time I enable my driver, I break into debugger. Any idea why?

Each time I enable/install my driver, it breaks into windbg with
the message.

nt!DbgLoadImageSymbols+0x47:
818437bb cc int 3

From the name, it looks like windbg is loading debug symbols for my driver.
But any idea why it breaks into windbg?
Is it possible to avoid this?

Thanks,
-Praveen

When this happened too me the other night, my symbol path was wrong. In
windbg, for an earlier version of
my driver it saved breakpoints in the workspace settings.

Not sure what exactly happened - but it seemed like windbg was trying to
execute a break point on the image,
but the sym path being wrong confused the debugger. (meaning, it knew it
needed to break somewhere, but not
sure where).

Every time I hit go

“nt!DbgLoadImageSymbols+0x47:
818437bb cc int 3”

would appear; the host and target both went into an infinite loop.

Fixing the sym path cleared up this problem for me.

Good luck,

m.

Praveen Kumar Amritaluru wrote:

Each time I enable/install my driver, it breaks into windbg with
the message.

nt!DbgLoadImageSymbols+0x47:
818437bb cc int 3

>From the name, it looks like windbg is loading debug symbols for my driver.
But any idea why it breaks into windbg?
Is it possible to avoid this?

Thanks,
-Praveen


Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

No, this is not my case… Src path/symbol path are all correct. All it needs
to be done is to give a “go”

Cheers,
-Praveen

“MM” wrote in message news:xxxxx@ntdev…
> When this happened too me the other night, my symbol path was wrong. In
> windbg, for an earlier version of
> my driver it saved breakpoints in the workspace settings.
>
> Not sure what exactly happened - but it seemed like windbg was trying to
> execute a break point on the image,
> but the sym path being wrong confused the debugger. (meaning, it knew it
> needed to break somewhere, but not
> sure where).
>
> Every time I hit go
>
> “nt!DbgLoadImageSymbols+0x47:
> 818437bb cc int 3”
>
> would appear; the host and target both went into an infinite loop.
>
> Fixing the sym path cleared up this problem for me.
>
> Good luck,
>
> m.
>
> Praveen Kumar Amritaluru wrote:
>
>>Each time I enable/install my driver, it breaks into windbg with
>>the message.
>>
>>nt!DbgLoadImageSymbols+0x47:
>>818437bb cc int 3
>>
>>>From the name, it looks like windbg is loading debug symbols for my
>>>driver.
>>But any idea why it breaks into windbg?
>>Is it possible to avoid this?
>>
>>Thanks,
>>-Praveen
>>
>>
>>—
>>Questions? First check the Kernel Driver FAQ at
>>http://www.osronline.com/article.cfm?id=256
>>
>>To unsubscribe, visit the List Server section of OSR Online at
>>http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>

Well, I assume you don’t have any breakpoints hard coded; I can only
recommend you
delete your current workspace and create a new one. Hopefully if that
doesn’t solve your
problem, someone else here will shed some light onto what is happening -
I’d like to know
for reference in the future.

m.

Praveen Kumar Amritaluru wrote:

No, this is not my case… Src path/symbol path are all correct. All it needs
to be done is to give a “go”

Cheers,
-Praveen

“MM” wrote in message news:xxxxx@ntdev…
>
>
>>When this happened too me the other night, my symbol path was wrong. In
>>windbg, for an earlier version of
>>my driver it saved breakpoints in the workspace settings.
>>
>>Not sure what exactly happened - but it seemed like windbg was trying to
>>execute a break point on the image,
>>but the sym path being wrong confused the debugger. (meaning, it knew it
>>needed to break somewhere, but not
>>sure where).
>>
>>Every time I hit go
>>
>>“nt!DbgLoadImageSymbols+0x47:
>>818437bb cc int 3”
>>
>>would appear; the host and target both went into an infinite loop.
>>
>>Fixing the sym path cleared up this problem for me.
>>
>>Good luck,
>>
>>m.
>>
>>Praveen Kumar Amritaluru wrote:
>>
>>
>>
>>>Each time I enable/install my driver, it breaks into windbg with
>>>the message.
>>>
>>>nt!DbgLoadImageSymbols+0x47:
>>>818437bb cc int 3
>>>
>>>>From the name, it looks like windbg is loading debug symbols for my
>>>
>>>
>>>>driver.
>>>>
>>>>
>>>But any idea why it breaks into windbg?
>>>Is it possible to avoid this?
>>>
>>>Thanks,
>>>-Praveen
>>>
>>>
>>>—
>>>Questions? First check the Kernel Driver FAQ at
>>>http://www.osronline.com/article.cfm?id=256
>>>
>>>To unsubscribe, visit the List Server section of OSR Online at
>>>http://www.osronline.com/page.cfm?name=ListServer
>>>
>>>
>>>
>>>
>
>
>
>—
>Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
>To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
>
>

Which version of windbg are you using and what is the target os?

There is an option in windbg to break on every module load event - which
is what it appears your debugger is doing. See Controlling Exceptions
and Events in the windbg help file.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Praveen Kumar
Amritaluru
Sent: Monday, August 07, 2006 8:44 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Each time I enable my driver, I break into debugger.
Any idea why?

No, this is not my case… Src path/symbol path are all correct. All it
needs
to be done is to give a “go”

Cheers,
-Praveen

“MM” wrote in message news:xxxxx@ntdev…
> When this happened too me the other night, my symbol path was wrong.
In
> windbg, for an earlier version of
> my driver it saved breakpoints in the workspace settings.
>
> Not sure what exactly happened - but it seemed like windbg was trying
to
> execute a break point on the image,
> but the sym path being wrong confused the debugger. (meaning, it knew
it
> needed to break somewhere, but not
> sure where).
>
> Every time I hit go
>
> “nt!DbgLoadImageSymbols+0x47:
> 818437bb cc int 3”
>
> would appear; the host and target both went into an infinite loop.
>
> Fixing the sym path cleared up this problem for me.
>
> Good luck,
>
> m.
>
> Praveen Kumar Amritaluru wrote:
>
>>Each time I enable/install my driver, it breaks into windbg with
>>the message.
>>
>>nt!DbgLoadImageSymbols+0x47:
>>818437bb cc int 3
>>
>>>From the name, it looks like windbg is loading debug symbols for my
>>>driver.
>>But any idea why it breaks into windbg?
>>Is it possible to avoid this?
>>
>>Thanks,
>>-Praveen
>>
>>
>>—
>>Questions? First check the Kernel Driver FAQ at
>>http://www.osronline.com/article.cfm?id=256
>>
>>To unsubscribe, visit the List Server section of OSR Online at
>>http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Target OS: Vista-5474.
Windbg version: 6.6003
Will read this section in windbg help file.

Thanks,
-Praveen

“Roddy, Mark” wrote in message news:xxxxx@ntdev…
Which version of windbg are you using and what is the target os?

There is an option in windbg to break on every module load event - which
is what it appears your debugger is doing. See Controlling Exceptions
and Events in the windbg help file.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Praveen Kumar
Amritaluru
Sent: Monday, August 07, 2006 8:44 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Each time I enable my driver, I break into debugger.
Any idea why?

No, this is not my case… Src path/symbol path are all correct. All it
needs
to be done is to give a “go”

Cheers,
-Praveen

“MM” wrote in message news:xxxxx@ntdev…
> When this happened too me the other night, my symbol path was wrong.
In
> windbg, for an earlier version of
> my driver it saved breakpoints in the workspace settings.
>
> Not sure what exactly happened - but it seemed like windbg was trying
to
> execute a break point on the image,
> but the sym path being wrong confused the debugger. (meaning, it knew
it
> needed to break somewhere, but not
> sure where).
>
> Every time I hit go
>
> “nt!DbgLoadImageSymbols+0x47:
> 818437bb cc int 3”
>
> would appear; the host and target both went into an infinite loop.
>
> Fixing the sym path cleared up this problem for me.
>
> Good luck,
>
> m.
>
> Praveen Kumar Amritaluru wrote:
>
>>Each time I enable/install my driver, it breaks into windbg with
>>the message.
>>
>>nt!DbgLoadImageSymbols+0x47:
>>818437bb cc int 3
>>
>>>From the name, it looks like windbg is loading debug symbols for my
>>>driver.
>>But any idea why it breaks into windbg?
>>Is it possible to avoid this?
>>
>>Thanks,
>>-Praveen
>>
>>
>>—
>>Questions? First check the Kernel Driver FAQ at
>>http://www.osronline.com/article.cfm?id=256
>>
>>To unsubscribe, visit the List Server section of OSR Online at
>>http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

You are right.
Read the windbg help section and disabled it.
Thanks,
-Praveen

“Praveen Kumar Amritaluru” wrote in message
news:xxxxx@ntdev…
> Target OS: Vista-5474.
> Windbg version: 6.6003
> Will read this section in windbg help file.
>
> Thanks,
> -Praveen
>
>
> “Roddy, Mark” wrote in message
> news:xxxxx@ntdev…
> Which version of windbg are you using and what is the target os?
>
> There is an option in windbg to break on every module load event - which
> is what it appears your debugger is doing. See Controlling Exceptions
> and Events in the windbg help file.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Praveen Kumar
> Amritaluru
> Sent: Monday, August 07, 2006 8:44 AM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Each time I enable my driver, I break into debugger.
> Any idea why?
>
> No, this is not my case… Src path/symbol path are all correct. All it
> needs
> to be done is to give a “go”
>
> Cheers,
> -Praveen
>
> “MM” wrote in message news:xxxxx@ntdev…
>> When this happened too me the other night, my symbol path was wrong.
> In
>> windbg, for an earlier version of
>> my driver it saved breakpoints in the workspace settings.
>>
>> Not sure what exactly happened - but it seemed like windbg was trying
> to
>> execute a break point on the image,
>> but the sym path being wrong confused the debugger. (meaning, it knew
> it
>> needed to break somewhere, but not
>> sure where).
>>
>> Every time I hit go
>>
>> “nt!DbgLoadImageSymbols+0x47:
>> 818437bb cc int 3”
>>
>> would appear; the host and target both went into an infinite loop.
>>
>> Fixing the sym path cleared up this problem for me.
>>
>> Good luck,
>>
>> m.
>>
>> Praveen Kumar Amritaluru wrote:
>>
>>>Each time I enable/install my driver, it breaks into windbg with
>>>the message.
>>>
>>>nt!DbgLoadImageSymbols+0x47:
>>>818437bb cc int 3
>>>
>>>>From the name, it looks like windbg is loading debug symbols for my
>>>>driver.
>>>But any idea why it breaks into windbg?
>>>Is it possible to avoid this?
>>>
>>>Thanks,
>>>-Praveen
>>>
>>>
>>>—
>>>Questions? First check the Kernel Driver FAQ at
>>>http://www.osronline.com/article.cfm?id=256
>>>
>>>To unsubscribe, visit the List Server section of OSR Online at
>>>http://www.osronline.com/page.cfm?name=ListServer
>>>
>>>
>>
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
>