similar to: WinDbg?

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?

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/tcp''.

> On Sep 7, 2017, at 11:37 AM, Zachary Turner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > 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

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 _______________________________________________ Xen-users mailing list

What is the status of debuginfo-tests? Is it actively supported? 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

As executable tests, they fail spectacularly in a cross-build environment. And you need some sort of debugger with GDB-like commands and output (or have some front end to your debugger that imitates that) in order to run them. I think they would need to stay in a separate project because of those requirements. --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of David

> On Sep 7, 2017, at 12:01 PM, Zachary Turner <zturner at google.com> wrote: > > > > On Thu, Sep 7, 2017 at 11:49 AM Adrian Prantl <aprantl at apple.com <mailto:aprantl at apple.com>> wrote: >> On Sep 7, 2017, at 11:37 AM, Zachary Turner via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> To

That's true, but it still requires the person writing the test to be familiar with both formats. Also anything more trivial than dumping a single local variable will probably run into even more issues. For example, The expression parsers each have their own unique quirks, and it might not always be easy to translate. Besides all the format compatibility issues, there's the more general

Even if it were under llvm, that doesn't mean it would have to be part of ninja check-all. Currently we have lldb/test and lldb/unittests, what about a third lldb/dbgtests? Then you could run it as ninja check-dbgtest. Although now that I think about it, we would want it to be able to invoke clang-cl directly, so I guess that does necessitate it *not* being under llvm. On Thu, Sep 7, 2017

What is the state of GPLPV and Windows 8? I am currently running tests with Windows 8 and GPLPV rev956 and operations (disk IO, net IO) look good. There seems to be a problem with shutdown/reboot where Windows hangs somewhat and displays a warning about improper shutdown on next reboot. Regards Andreas

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): 0x400000 - 0x400fff c-r-- (PAGE_READONLY) 0x401000 - 0x454fff c--W- (PAGE_WRITECOPY)

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 program installed handle the exception. And the program does

Hi all, I've recently been doing some work on a novel language that uses LLVM for optimization and machine codegen. The language is self-hosted, 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,

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

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:

I currently have two VMs communicating with each other. One is XP, the other is QNX. I added a serial port to each of the VMs that maps to /tmp/com_1. So each VM thinks it's communicating over its serial port. This communication works great, but the XP VM is super slow. So I thought I'd try Wine. So far it seems to work, but the communication doesn't. How can I get this communication

Hi, I am a newbe with Wine and I need some advice.. I have 2 partitions on my computer: Linux + winnt40. I use wine for developping drivers for W2K (yes it is NOT a joke!) under Linux (some kinda of cross-compiling if you want ..). So for compiling and linking it works flawlessly (really!) and it's GREAT! The only problem is that I cannot browse the DDK documentation. For doing that

Hi, Is there any way to debug the codeview output of llvm from within Visual Studio? I want to use the codeview line info debug 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.

Patches item #6236, was opened at 2006-10-19 07:10 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=413&aid=6236&group_id=85 >Category: windows-pr Group: None Status: Open Resolution: None Priority: 3 Submitted By: Jano Svitok (janek) >Assigned to: Daniel Berger (djberg96) Summary: Add debug API Initial Comment: This adds couple of methods to