similar to: Rgui.exe plot device "Save as" crash (PR#9237)

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.ufies.org/lotr0/windbg-vmware.html), and then tried my hands

Full_Name: Davide Fiaschi Version: R 1.3.1 and 1.2.3 OS: Windows 2000 Submission from: (NULL) (131.114.67.164) When I try to start RGUI, it generates an error in application and R chashs. (NOTE: R worked very well with trial version of Windows 2000!) Here is the (not very informative form me) Dr Watson's report: Exception dell'applicazione: App: (pid=1140) Ora:

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

Dear listers, Am currently using MCMC approaches to estimate some parameters of my model. One parameter has to be updated using a tuned gamma distribution. So at each iteration I estimate the mean and variance of the density of the gamma approximation using "vmmin" (i also supply the gradient argument). For moderate replications the procedure works, but if I increase them R crashes.

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

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?

Dear All, I haven't seen any further comments about the problem that John Marsland first noted and that I also have: > library(DBI) > library(RMySQL) Warning message: DLL attempted to change FPU control word from 8001f to 9001f > mgr <- dbDriver("MySQL") > con <- dbConnect(mgr, host="localhost", dbname="marketing") upon which R dies...

> 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

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

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

> 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

Hi, I have questions about object attributes, and how they are handled when subsetted. My examples will use: tm <- (1:10)/10 ds <- (1:10)^2 attr(tm,"units") <- "sec" attr(ds,"units") <- "cm" dat <- data.frame(tm=tm,ds=ds) attr(dat,"id") <- "test1" When a "primitive class" object (numeric, character, etc.) is

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

Full_Name: Oren Cheyette Version: 2.7.2 OS: Win XP Submission from: (NULL) (64.161.123.194) Enter the following at the R command prompt: > sprintf("A %S %S %S XYZ", 1, 1, 1); Note the erroneous capitalized %S instead of %s and the numeric inputs instead of strings. With strings there's no crash - R reports bad format specifications.

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

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)

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:

It installed correctly, however when trying to run, I briefly get a window appearing, and then it crashes. A trace reveals: <snip> fixme:ole:MSFT_DoTypeInfo Assign constructor/destructor memid fixme:ole:CoRegisterMessageFilter stub wine: Unhandled exception, starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /mnt/fd0 (No such file or

Dear List: First, many thanks to those who offered assistance while I constructed code for the simulation. I think I now have code that resolves most of the issues I encountered with memory. While the code works perfectly for smallish datasets with small sample sizes, it arouses a windows-based error with samples of 5,000 and 250 datasets. The error is a dialogue box with the following: "R