search for: windbg

Hello, I have been struggling with WinDbg/Kd for the last week, but to no avail... So I finally decided to ask here. Basically, I am using a Windows XP virtual machine (thanks to VMWare6) and wanted to do some kernel debugging using Windbg. So, I did configure everything from the virtual machine side (using this guide: http://silverstr.uf...

hi, I am using xen-unstable version and I can use the serial port to debug DomU openSuSE Linux with kgdb very well. But it doesn''t work when I am trying to debug DomU WinXP with windbg. I happened to find this link http://www.evilbitz.com/2006/12/13/howto-debugging-a-remote-windows-hvm-under-xen-using-windbg/, but it still doesn''t work for me. Any suggestions about this? Thanks, Neo -- I would remember that if researchers were not ambitious probably today we haven...

...ported? How do you run it? It doesn't appear to be based on lit, any particular reason? Why is it its own repo instead of being part of llvm repo? I'd like improve this to support CodeView and PDB, such that it would only run on Windows and only if a suitable debugger was found (probably WinDbg). WinDbg supports a JavaScript-based scripting model, similar to how LLDB supports a Python based model, so my thoughts were to have a lit-based runner that scans for .js files that contain a test script alongside some source, then build the program, run it in WinDbg with some script that does var...

I found this article on http://wiki.xensource.com/xenwiki/XenWindowsGplPv, but windbg display com8 reconnect forever. AND RxBytes always 0. Thank you Using the windows debugger under Xen Set up Dom0 1. Change/add the serial line to your Windows DomU config to say serial=''pty'' 2. Add a line to /etc/services that says ''windbg_domU 4440...

...orted? How do you run it? It doesn't appear to be based on lit, any particular reason? Why is it its own repo instead of being part of llvm repo? I'd like improve this to support CodeView and PDB, such that it would only run on Windows and only if a suitable debugger was found (probably WinDbg). WinDbg supports a JavaScript-based scripting model, similar to how LLDB supports a Python based model, so my thoughts were to have a lit-based runner that scans for .js files that contain a test script alongside some source, then build the program, run it in WinDbg with some script that does var...

...te: > > To be clear, the tests I'm proposing will have no resemblance whatsoever to GDB, so I would be intentionally forking the set of tests in this regards. So there would very clearly be a paradigm shift in writing CodeView debug info tests (which would be written in JavaScript using WinDbg specific debugger commands) and DWARF debug info tests (which would be written in whatever / using GDB style commands) That sounds like an unfortunate direction. Can you explain why it wouldn't be possible to write a wrapper (in JavaScript) that interprets the 3ish gdb commands used by the tes...

Hi, Is it possible to connect windbg to guest windows 2008 R2, over xen? Anyone how did it succesfully? I tried steps in this links http://wiki.xensource.com/xenwiki/XenWindowsGplPv but it''s not working for me :( (i modified add in xinited, instead of inetd.conf) Can any1 update this doc? Regards, Piyush ___________________...

...s to go wrong and/or be flaky. But as we are the ones that have to do the massaging, we get the short end of the stick. One possible bridge is to make some sort of special directive that identifies a certain fragment of the test file as gcc input & checks, and another directive that identifies windbg input & checks. This way each could have their own native run lines, debugger commands, and check statements, but share the same source code. The runner then chooses which mode to run based on which directives are present and whether a debugger to run the corresponding fragment in is found. T...

...> >> To be clear, the tests I'm proposing will have no resemblance whatsoever to GDB, so I would be intentionally forking the set of tests in this regards. So there would very clearly be a paradigm shift in writing CodeView debug info tests (which would be written in JavaScript using WinDbg specific debugger commands) and DWARF debug info tests (which would be written in whatever / using GDB style commands) > > That sounds like an unfortunate direction. Can you explain why it wouldn't be possible to write a wrapper (in JavaScript) that interprets the 3ish gdb commands used...

...appear to be based on lit, any particular reason? >> Why is it its own repo instead of being part of llvm repo? >> >> I'd like improve this to support CodeView and PDB, such that it would >> only run on Windows and only if a suitable debugger was found (probably >> WinDbg). WinDbg supports a JavaScript-based scripting model, similar to >> how LLDB supports a Python based model, so my thoughts were to have a >> lit-based runner that scans for .js files that contain a test script >> alongside some source, then build the program, run it in WinDbg wit...

Hey all, I plan to use windbg tool to do remote debug my Windows PV Driver. I''m confused how to setup the enviroment. Any Advice? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hey all, I plan to use windbg tool to do remote debug my Windows PV Driver. I''m confused how to setup the enviroment. Any Advice? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...ery near the beginning of the program. I think this corresponds to the EXCEPTION_FRAME structure in include/winnt.h, so that 0x761B10 is the exception handler, and eax (fs:0) is the previous exception frame. Then there's some extra data, 0x75A010 and -1 at the end of the frame data. I used WinDbg to step through the code running under W2K, setting a breakpoint at 0x761B10. Running the code, it caught an access violation at a place neither wine nor gdb caught in a piece of code that seems obviously designed to look for an access violation: 0075F0D7 mov eax, 75F07Eh 00...

Full_Name: Michael Toews Version: 2.3.1 OS: WindowsXP Home/Proffesional SP2 Submission from: (NULL) (142.58.206.114) Hi, I have a bug that I can reproduce on two different MS Windows platforms (1:AMD64x2/WinXP SP2 Home; 2:P4/WinXP SP2 Prof.) which is triggered by the "Save as" dialog when saving a plot from a Windows device onto the Desktop. This bug is difficult to reproduce, but here

I used WinDbg to show the memory protections that were placed on the executable image just after it was loaded, and just before the app starts. Here is what wine shows: View: 0x400000 - 0x765fff 28 0x400000 - 0x765fff c-rw- Here is what WinDbg shows (manually edited to look like the wine view): 0x400...

I downloaded (shudder) Microsoft's windbg program (http://www.microsoft.com/ddk/debugging/installx86beta.asp) and ran it for the app under Win2000/VMWare. It also shows an exception at the same access! However, windbg displays the exception and then allows the user to continue the program, letting whatever exception handler the progra...

Trying to install them on Xen 3.4.0, Intel E5345 Processors, Server 2008 64bit. I get the BSoD on boot with the 0x0000007B stop message. I''ve got a bunch of 2003 32bits running on the same host with the 0.10.0.69 drivers and those are totally happy. I tried the boot once with NOGPLPV idea mentioned in another thread, that didn''t do the trick. Ideas anyone? pace

...sted, I'm building my third iteration of its garbage collector, and also writing a thin IDE to stretch the language a bit. Needless to say, debugging is a major concern for me. My primary experience (and primary development focus) is Windows-centric, so my go-to debuggers are Visual Studio and WinDbg. I know of the lldb/VS integration efforts, and of course with appropriate setup I could also leverage gdb (IIRC). But these aren't quite what I was looking for, personally. Long story short I set out to build a PDB emitter that could generate debug information for my language based on the exi...

Hello! After having a large feud with gdb, I decided to switch over to lldb under Windows like I already had under Linux. However, when I installed it using the 64-bit LLVM nightly installer, it kept crashing upon startup. Popping it in WinDbg (oh the irony) showed that it was trying to load Python35.dll, but it was loading the 32-bit version I had installed separately. The fix was simple: download the Python 3.5 binary ZIP and copy python35.dll to the LLVM bin directory. TL;DR: The nightly installer is missing python35.dll, meaning th...

...ug output of clang/llvm. I tried with the x86_64-pc-windows-msvc and i686-pc-windows-msvc triples and linking it into an existing project with VC++ from within the IDE and outside with link /debug. Neither option lets me debug with Visual Studio as debugger host. With some help I found that WinDBG does show line info, but Visual Studio does not, is there any way to get this working with VS? -- Carlo Kok RemObjects Software