X86 Debug registers

Discussion in 'Virtual PC' started by Cactus Jack, Dec 12, 2003.

  1. Cactus Jack

    Cactus Jack Guest

    I couldn't find a mention anywhere in the tech ref or a
    search of this site, but is there any support for the X86
    hardware debug registers in VPC? A test drive of Netware 6
    was going pretty well until I tried to enter the Netware
    debugger and set a breakpoint (which uses the 4 debug
    registers). The breakpoint never "hit", and yet the p/step
    over and t/step into commands seemed to work (which I
    thought also used the debug registers).

    Thanks in advance
    JGS
     
    Cactus Jack, Dec 12, 2003
    #1
    1. Advertisements

  2. Which version of VPC are using using? We have limited support for the debug
    registers, but certainly execution and memory write breakpoints should work
    in VPC 2004.
    --
    Aaron Giles
    Virtual PC dev lead
    Microsoft Corp.
    Legal: This posting is provided "AS IS" with no warranties, and confers no
    rights.
     
    Aaron Giles [MSFT], Dec 13, 2003
    #2
    1. Advertisements

  3. Cactus Jack

    Cactus Jack Guest

    I'm using Virtual PC 2004 (Build 582) as downloaded from
    MSDN. Using Win2K, SP4. CPU: Intel P-IV, 3.0 Ghz, 1 Gb
    PC3200 Ram, Intel D865GBF mother board. Yes, I did test
    this running real, and Netware breakpoints work OK.

    The debugger is the Netware 6 Console debugger (hold L-
    SHIFT, R-SHIFT, L-ALT, and ESC to get in). Type H or HB to
    get help on breakpoints. B = xxx to set break at xxx. U or
    U xxx does disasemble. I can type "b = xxx" at some inline
    piece of code, "u xxx" to verify where I'm going, then "g"
    to go and it just "goes" without ever hitting the break. I
    don't know if Novell is setting up debug regs in some
    unusual way. All I know is I've only got 4 breakpoints (=>
    using debug registers), and debugger says there "global"
    and "execution" breakpoints, when list with "b" command.
     
    Cactus Jack, Dec 13, 2003
    #3
  4. Cactus Jack

    Cactus Jack Guest

     
    Cactus Jack, Dec 17, 2003
    #4
  5. Cactus Jack

    Cactus Jack Guest

    Let's try this again... (please remove previous redundant
    post of 12/17)

    Dear Aaron:

    Down here in Tucson, one gets used to a slower-moving
    lifestyle. However, I
    was sort of hoping for a response to my last post by now.
    I was hoping for a
    "yes, that's a bug we're fixing", or a "yes, we can
    reproduce the problem", or
    at least "we're checking it out", but even a "you're nuts"
    or "go away, and
    don't bother us with any more non-Windows simulation
    problems" response would
    be helpful.

    Did I commit an inadvertent faux pas by mentioning the "N
    word" (Novell)? Or
    should I have ended my last post with a question mark?
    Also, "... limited
    support ... for the debug registers..." is a little vague,
    and leaves me with
    nothing to think about or experiment with on this end. Can
    you be more
    specific about the VPC limitations in this area?

    So, how can we move forward on this, or at least close it
    out? Will you try to
    reproduce the problem, or are we at an impasse?
     
    Cactus Jack, Dec 17, 2003
    #5
  6. Cactus Jack

    SJ Guest

    it you need iimmediate support, maybe you should open a case with PSS
    instead of the user forums.
     
    SJ, Dec 17, 2003
    #6
  7. If this is a high priority item, I strongly suggest you contact PSS and open
    a case with them. Reading/posting to these groups is not my day job.

    As for your specific problem, I meant just what I said: execution and memory
    write breakpoints should work. They have been tested in kd and work fine. I
    have never tried them in Novell. Memory read/write breakpoints will only
    function as memory write breakpoints. And I/O breakpoints will not work. If
    this is not what you are seeing, there is probably a bug lurking somewhere.
    Again, this should be logged through the proper channels.
    --
    Aaron Giles
    Virtual PC dev lead
    Microsoft Corp.
    Legal: This posting is provided "AS IS" with no warranties, and confers no
    rights.
    --
     
    Aaron Giles [MSFT], Dec 17, 2003
    #7
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.