In our special case, windbg seems cannot hit the break point. (Sorry i don’t know much details, but basically windbg cannot debug well in our case.)
So is there any good hardware debugger for 64 bit ?
Windbg does not have a problem with 64bit. Before you spend 50-150K+
on a hardware debugger, you might want to get the details on why
windbg is not working for you.
Mark Roddy
On Fri, Nov 19, 2010 at 6:13 PM, wrote:
> In our special case, windbg seems cannot hit the break point. (Sorry i don’t know much details, but basically windbg cannot debug well in our case.)
>
> So is there any good hardware debugger for 64 bit ?
>
> —
> NTDEV 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
>
I think that this discussion is better suited to the windbg forum. In any
event, this is also my experience that windbg is a LOT more reliable on the
x86 platform than on x64. I usually end up inserting KdBreakPoint into the
code where I want it to break. THEN it does break reliably; and it is
cheaper than a hardware debugger. I don’t know whether it is Windbg or the
OS which is the problem, since Windbg relies on the OS kernel.
Windbg requires the correct symbols to be loaded to work properly. Are you
sure that the correct symbols are loaded for the code in which you wish to
break?
Regards,
George.
wrote in message news:xxxxx@ntdev…
> In our special case, windbg seems cannot hit the break point. (Sorry i
> don’t know much details, but basically windbg cannot debug well in our
> case.)
>
> So is there any good hardware debugger for 64 bit ?
>
Well I simply disagree. I routinely use windbg with a variety of
windows releases, both 32 and 64bit, and there simply is no difference
in windbg reliability between 64bit and 32bit on the same platform.
The only issues I have with windbg are connecting through firewire.
Mark Roddy
On Fri, Nov 19, 2010 at 6:59 PM, George M. Garner Jr.
wrote:
> I think that this discussion is better suited to the windbg forum. ?In any
> event, this is also my experience that windbg is a LOT more reliable on the
> x86 platform than on x64. ?I usually end up inserting KdBreakPoint into the
> code where I want it to break. ?THEN it does break reliably; and it is
> cheaper than a hardware debugger. ?I don’t know whether it is Windbg or the
> OS which is the problem, since Windbg relies on the OS kernel.
>
> Windbg requires the correct symbols to be loaded to work properly. ?Are you
> sure that the correct symbols are loaded for the code in which you wish to
> break?
>
> Regards,
>
> George.
>
> wrote in message news:xxxxx@ntdev…
>> In our special case, windbg seems cannot hit the break point. (Sorry i
>> don’t know much details, but basically windbg cannot debug well in our
>> case.)
>>
>> So is there any good hardware debugger for 64 bit ?
>>
>
>
>
> —
> NTDEV 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
>
Before buying quite expensive piece of equipment which hardware debuggers usually are, I would suggest to first define the problem you are trying to solve here. Do you actually need to have debug step / breakpoint functionality or you just want to examine some data structures at some arbitrary point in time?
If second then you have several options:
- Generate memory dumps with livekd (from sysinternals)
- Generate memory dumps with either helper driver or key sequence (google CrashOnCtrlScroll)
- Examine live system with windbg in local mode
If you want to trace execution flow or examine some data at specfic point in time you can employ debug prints (use DebugView on your target system) or ETW/WPP or some other tracing mechanism.
If you really need live debugging with breakpoints and everything then maybe it?s worth to get more information about what?s actually going wrong. What kind of debug transport are we talking about here? Is it serial, firewire or USB? Can you actually break-in to the system manually (ctrl+break)? Did you try to hardcode a breakpoint (__debugbreak()/DbgBreakPoint)? What do you get when you turn on debug info (ctrl+alt+d)?
Also there should be not much difference between x86 and x64 debugging. From my experience if KD works on x86 it also works on x64, so maybe there is something wrong with your KD configuration (check bcdedit or boot.ini) or hardware (cables, etc.).
Kris
Gotta agree with Mark.
Why not explain what you’re doing instead of making a blatant assumption
that the rest of us know is simply not true. WinDbg is not the best
debugger, but it does work on 64 bit. Most likely you have a silly little
error such as building for free instead of checked, or not using the latest
debugger, or not having your symbols set correctly.
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mark Roddy
Sent: Friday, November 19, 2010 5:26 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Any good hardware for 64-bit windows 7 ?
Windbg does not have a problem with 64bit. Before you spend 50-150K+
on a hardware debugger, you might want to get the details on why
windbg is not working for you.
Mark Roddy
On Fri, Nov 19, 2010 at 6:13 PM, wrote:
> In our special case, windbg seems cannot hit the break point. (Sorry i
don’t know much details, but basically windbg cannot debug well in our
case.)
>
> So is there any good hardware debugger for 64 bit ?
>
> —
> NTDEV 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
>
—
NTDEV 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
Information from ESET Smart Security, version of virus signature
database 5634 (20101119)
The message was checked by ESET Smart Security.
http://www.eset.com