similar to: Attaching GDB to Tapdisk for Debugging

Hi everyone, as what I''ve learned form this link<http://wiki.xensource.com/xenwiki/blktap>, i know that when i specify tap:aio I’m actually using the blktap driver and finally using "tapdisk" to wirite to raw image file. but the truth is even when i delete /usr/sbin/tapdisk the domU can still boot on my machine with tap:aio protocol after a deeper look into the scene,

Hi All, I'm seeing tapdisk processes not being terminated after a HVM vm is shutdown or migrated away. I don't see this problem with linux paravirt domu's, just windows hvm ones. xl.cfg: name = 'nathanwin' memory = 4096 vcpus = 2 disk = [ 'file:/mnt/gtc_disk_p1/nathanwin/drive_c,hda,w' ] vif = [ 'mac=00:16:3D:01:03:E0,bridge=vlan208' ] builder =

On Mon, Sep 21, 2009 at 10:08:34AM -0700, Chris Lattner wrote: > > On Sep 21, 2009, at 6:16 AM, Jack Howarth wrote: > >> The gdb developers are rapidly approaching the >> release of gdb 7.0 (which will be required to debug > > Hi Jack, > > I know you're trying to help improve tools for Darwin, but llvm-dev is > not really an appropriate place for it.

The gdb developers are rapidly approaching the release of gdb 7.0 (which will be required to debug optimized code generated by gcc 4.5 due changes related to the var tracking association merge and other code). They currently have patches proposed that allows gdb 7.0 to debug code in darwin9.6. However there was some change made in darwin9.8 and darwin10 which no longer allows the previous

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, while trying to get blktap based domus running with current Debian Xen 3.1.2 I came across a missing link: The tapdisk binary should be added to GLOBAL_SCRIPTS in xen-common/scripts/Makefile. Otherwise blktap based domus don't find their disks. blktapctrl forks tapdisk processes. Peter -----BEGIN PGP SIGNATURE----- Version: GnuPG

The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS:

The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS:

On Sep 21, 2009, at 6:16 AM, Jack Howarth wrote: > The gdb developers are rapidly approaching the > release of gdb 7.0 (which will be required to debug Hi Jack, I know you're trying to help improve tools for Darwin, but llvm-dev is not really an appropriate place for it. Please stick to LLVM related topics on this list where possible. -Chris

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1316609964 -3600 # Node ID b43fd821d1aebc8671e684bfc285cda7a6002ff1 # Parent 206afa070919e3fe0b13a03f870ca2da44ab604a libxl: attempt to cleanup tapdisk processes on disk backend destroy. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> diff -r 206afa070919 -r b43fd821d1ae

Although tapdisk has been instead of tapdisk-ioemu, but it still used on some old xen-3.2. So fix a performance problem here. -- Kernel aio will retry when encounter a block doesn''t allocated, then do async io, but O_DIRECT flag was there, so io_wait on sync data. And clean a little code style. Signed-off-by: Wei Kong <weikong.cn@gmail.com>

On Thu, Mar 12, 2015 at 6:11 PM, Nathan March <nathan at gt.net> wrote: > Hi All, > > > > I'm seeing tapdisk processes not being terminated after a HVM vm is shutdown > or migrated away. I don't see this problem with linux paravirt domu's, just > windows hvm ones. Interesting -- actually you get the same effect just starting and shutting down a guest. It

stubdom: do not build tapdisk as it it not supposed to build and we don''t need it Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 4024164e7572 stubdom/Makefile --- a/stubdom/Makefile Tue Jul 08 16:11:49 2008 +0100 +++ b/stubdom/Makefile Tue Jul 08 17:12:38 2008 +0100 @@ -190,7 +190,7 @@ [ -f ioemu/config-host.mak ] || \ ( cd ioemu ; \

When a domain wants to use a tap:ioemu disk but has no device model, start a tapdisk-ioemu instance as provider. Also, move the creation and removal of communication pipes to xend so that qemu-dm doesn''t need the unwanted SIGHUP handler anymore. Signed-off-by: Kevin Wolf <kwolf@suse.de> _______________________________________________ Xen-devel mailing list

I tried to run gdb in linux with emacs But could not even run a simple example in the writing extensions tutorial. The execution history is as follows. Gdb worked fine for other debugging such as C++ codes. Thanks Han I started R at echo of emacs by typing (also tried other methods mentioned in the tutorial both in emacs and xterm.) M-x gdb ==> R -d gdb (gdb) run Starting program:

I'm trying to follow the example in the R for Windows FAQ on running gdb and am getting stuck because gdb tells me "Cannot access memory at address ...". Here's what my gdb session looks like (This one from a cygwin shell, but same results from plain Windows CMD shell): $ cd R-devel/src/gnuwin32 $ gdb ../../bin/Rgui.exe GNU gdb 5.2.1 Copyright 2002 Free Software Foundation,

Pranav Garg wrote: > Hi, > > I am trying to debug my llvm pass called -aa-eval-garg11 using gdb. > However I am not able to establish a breakpoint in any function of my > pass. I have compiled my > pass with a debug build and I have also compiled the input file (using > llvm-gcc) with the -g flag. Given below is the exact output. > > > (gdb) break

Are you debugging the driver process or the -cc1 process? To get the -cc1 process, unfortunately you have to go through the dance of passing -### to get the -cc1 line and then run that in gdb (or write one manually). Alternatively in gdb you can say "set follow-fork child" (or something, check the docs) to automatically follow into the -cc1 child. On Tue, May 21, 2013 at 8:00 AM,

Hi all, I would like to be able to debug opt passes. - I compiled llvm in debug mode - gdb /usr/local/bin/opt - run opt -load /path/to/LLVMHello.so -hello <any.bc> /dev/null and then get /usr/local/bin/opt: opt: err: Could not open input file .... could it be the <> syntax is not gdb command window conform? I tried to find out if i could provide opt in and out files using standard

On 3 December 2012 10:42, Mayur Pandey <mayurthebond at gmail.com> wrote: > So this seems to be the cause of the problem. I guess you're mixing two different problems. First, is the possible lack of conformance with the ABI you state, which I can't comment since I don't know that ABI very well. Second, is the fact that clang is not printing correct debug information (or is

Hi John, Yes, it was the problem of the namespace. Sorry for bugging for such a silly mistake. Thanks Pranav On Mon, Apr 19, 2010 at 9:33 AM, John Criswell <criswell at uiuc.edu> wrote: > Pranav Garg wrote: > >> Hi, >> >> I am trying to debug my llvm pass called -aa-eval-garg11 using gdb. >> However I am not able to establish a breakpoint in any function of