search for: addlabels

Hi all, Could you teach me about the behavior of xm commands when ''ACMError'' occurred? I am testing the behavior of xm commands with wrong arguments. When I tested xm commands related to security (xm *label/*policy), I found that some of them. - return 0, - show ACMError''s Traceback messages. Are these results specifications or bugs? Example: # xm cfgbootpolicy

On Feb 24, 2011, at 11:52 AM, Devang Patel wrote: > > On Feb 24, 2011, at 11:36 AM, Devang Patel wrote: > >> >> On Feb 12, 2011, at 2:07 AM, Nathan Jeffords wrote: >> >>> Hello All, >>> >>> I have created a set of patches that get dwarf debugging support working for the COFF object file. I also believe I have fixed what appears to be a

On Feb 24, 2011, at 11:36 AM, Devang Patel wrote: > > On Feb 12, 2011, at 2:07 AM, Nathan Jeffords wrote: > >> Hello All, >> >> I have created a set of patches that get dwarf debugging support working for the COFF object file. I also believe I have fixed what appears to be a bug in how line info sections are referred to from the DW_TAG_compile_unit DIE. I have run

Using R 2.5.1 on Windows XP Professional, and PBSmapping package version 2.51, I have encountered some behavior which puzzles me. I am including the package's listed maintainer on this email but also seek the thoughts of the R-help community. I have a set of EventData, which I want to plot as points, and to color the points according to some criterion. It turns out that some of my

W dniu 2012-10-26 16:55, Daniel Kłobuszewski pisze: > Hello, > > Recently I found binaries produced with LLVM impossible to debug under > Windows. This was probably related to the following bug: > http://llvm.org/bugs/show_bug.cgi?id=13636 > > Asm generated from .ll files revealed that some offsets to debug > information were incorrect: they were absolute instead of

Hello, Recently I found binaries produced with LLVM impossible to debug under Windows. This was probably related to the following bug: http://llvm.org/bugs/show_bug.cgi?id=13636 Asm generated from .ll files revealed that some offsets to debug information were incorrect: they were absolute instead of relative to their sections. Following patch seemed to have repaired the problem, so I'm

I have an installation of 32bit SLES 10.1 on 2 servers in my lab that I just rebuilt. I applied the files from xen-3.1.0-install-x86_32.tgz and broke all the virtman functions. The errors I got indicate some missing python classes, specifically xen.install. I''m not sure why. This is what I get when I try to run virtman from the command line. If I try to run it from yast i get nothing.