search for: debugger

...050111 wine is executed as wine Parameters are --noexit Version of Wine is OK. Calls to wine are executed as wine. Config is /home/webster/.wine/winetools.log. CDROM is /mnt/cdrom. Choice is Install Windows system software \*new\* fake Windows drive wine: Unhandled exception (thread 0009), starting debugger... wine: Unhandled exception (thread 000b), starting debugger... wine: Unhandled exception (thread 000d), starting debugger... wine: Unhandled exception (thread 000f), starting debugger... wine: Unhandled exception (thread 0011), starting debugger... wine: Unhandled exception (thread 0013), startin...

This is basically a reboot of the previous thread titled About the "debugger target" except that "target" was really too strong a term for what I had intended to use this feature for. "Debugger tuning" is more like it. You don't need to have read the previous thread, I'll recap here. Fundamentally, Clang/LLVM uses DWARF as the specificati...

> A few more things that vote for debugger tuning: > > - LLDB doesn't like to have DWARF that has a class A that inherits from > class B, but only a forward declaration of class B is provided. Hmm do we emit that kind of thing today? In a naïve test, I'm seeing the full description of class B. > - LLDB wants the .app...

Another example would be .debug_pubnames and .debug_pubtypes sections. Currently these default to omitted for Darwin and PS4, but included everywhere else. My initial patch for "tuning" changes the PS4 platform criterion to the SCE debugger predicate; quite likely the "not Darwin" criterion ought to be "not LLDB" or in other words "on for GDB only." "not LLDB" wouldn't be "on for GDB only" (it'd be "on for GDB and SCE" given the current debuggers) Poorly phrased on...

> On May 1, 2015, at 2:18 PM, Greg Clayton <gclayton at apple.com> wrote: > > >> On May 1, 2015, at 2:00 PM, Robinson, Paul <Paul_Robinson at playstation.sony.com> wrote: >> >>> A few more things that vote for debugger tuning: >>> >>> - LLDB doesn't like to have DWARF that has a class A that inherits from >>> class B, but only a forward declaration of class B is provided. >> >> Hmm do we emit that kind of thing today? In a naïve test, I'm seeing >> the full...

Hello list, I successfully installed Morrowind. Unfortunately, the game won't start. It issues a small popup saying a debugger has been detected, and that the debugger needs to be closed for the game to run. Is there any way I can avoid programs to see Wine as a debugger? Thanks! _________________________________________________________________ MSN Messenger : discutez en direct avec vos amis ! http://messenger.fr.ms...

....com <mailto:gclayton at apple.com>> wrote: > > > > > >> On May 1, 2015, at 2:00 PM, Robinson, Paul <Paul_Robinson at playstation.sony.com <mailto:Paul_Robinson at playstation.sony.com>> wrote: > >> > >>> A few more things that vote for debugger tuning: > >>> > >>> - LLDB doesn't like to have DWARF that has a class A that inherits from > >>> class B, but only a forward declaration of class B is provided. > >> > >> Hmm do we emit that kind of thing today? In a naïve test, I'm se...

I just skimmed through the thread again, and I *think* all the main questions have been answered… It feels like the consensus is "reluctant agreement," with the specific design points being: - a "debugger tuning" option would have some sort of target-based default - the "debugger tuning" option would unpack into defaults for individual feature flags - emitting actual DWARF would test the feature flags not the tuning option - any command-line options for feature...

Hi All, I'd like to revisit the MCJIT debugger-registration system, as the existing system has a few flaws, some of which are seriously problematic. The 20,000 foot overview of the existing scheme (implemented in llvm/lib/ExecutionEngine/RuntimeDyld/GDBRegistrar.cpp and friends), as I understand it, is as follows: We have two symbols in MCJIT...

Hi When compiling UnixLocalInferiorProcess.cpp, I get these errors: ----------------------- C:/MinGW/msys/local/projects/src/llvm/lib/Debugger/UnixLocalInferiorProcess.cpp:41:22: sys/wait.h: No such file or directory C:/MinGW/msys/local/projects/src/llvm/lib/Debugger/UnixLocalInferiorProcess.cpp: In member function `void <unnamed>::IP::startChild(llvm::Module*, const std::vector<std::string, std::allocator<std::string&...

...t cs.uiuc.edu] On Behalf Of Adrian Prantl Sent: Friday, May 08, 2015 10:11 AM To: Robinson, Paul Cc: lldb-dev at cs.uiuc.edu; cfe-dev at cs.uiuc.edu Developers (cfe-dev at cs.uiuc.edu); LLVM Developers Mailing List (llvmdev at cs.uiuc.edu) Subject: Re: [LLVMdev] [lldb-dev] [cfe-dev] What does "debugger tuning" mean? > On May 8, 2015, at 7:24 AM, Robinson, Paul <Paul_Robinson at playstation.sony.com> wrote: > > Comments on the patch raise the following questions, probably better discussed here. > > First: Should LLVM default to "no tuning" rather than a tar...

Hi guys, I have been using a debugger for my register allocator. The debugger happened to be very useful at catching register assignment errors. I've put the debugger on-line, if anyone who is working with register allocation wants to use. The debugger itself has nothing to do with LLVM, but I've coded a spiller that prints...

...o:Paul_Robinson at playstation.sony.com>> wrote: > I just skimmed through the thread again, and I *think* all the main questions have been answered… > > It feels like the consensus is "reluctant agreement," with the specific design points being: > > - a "debugger tuning" option would have some sort of target-based default > > - the "debugger tuning" option would unpack into defaults for individual feature flags > > - emitting actual DWARF would test the feature flags not the tuning option > > - any co...

...Berlin [mailto:dberlin at dberlin.org] > Sent: Friday, May 01, 2015 3:15 PM > To: Robinson, Paul > Cc: cfe-dev at cs.uiuc.edu Developers (cfe-dev at cs.uiuc.edu); LLVM Developers > Mailing List (llvmdev at cs.uiuc.edu); lldb-dev at cs.uiuc.edu > Subject: Re: [LLVMdev] What does "debugger tuning" mean? > > On Fri, May 1, 2015 at 1:06 PM, Robinson, Paul > <Paul_Robinson at playstation.sony.com> wrote: > > > > > LLVM already emits DWARF slightly differently for different *targets*; > > primarily Darwin, in a few cases PS4. But in at least so...

...haven't gotten there yet. If you come up with something that works on MINGW, please let me know. Thanks, Reid. Henrik Bach wrote: > Hi > > When compiling UnixLocalInferiorProcess.cpp, I get these errors: > ----------------------- > C:/MinGW/msys/local/projects/src/llvm/lib/Debugger/UnixLocalInferiorProcess.cpp:41:22: > sys/wait.h: No such file or directory > C:/MinGW/msys/local/projects/src/llvm/lib/Debugger/UnixLocalInferiorProcess.cpp: > In > member function `void <unnamed>::IP::startChild(llvm::Module*, const > std::vector<std::string, std::al...

On 18 October 2012 02:53, Robinson, Paul <Paul.Robinson at am.sony.com> wrote: > I had a "quality suite" at a previous job; it was the result of many PY > of effort. It was also debugger-based, which is a mixed blessing; you > get a lot of DWARF-parsing code for free, but then you get a lot of > debugger bugs for free too! And you don't get to test the DWARF > directly, you get to test how the debugger uses the DWARF. Not really > optimal, but still--a whole lot be...

...half Of Robinson, Paul Sent: Wednesday, May 06, 2015 2:40 PM To: Adrian Prantl; Eric Christopher Cc: lldb-dev at cs.uiuc.edu; cfe-dev at cs.uiuc.edu Developers (cfe-dev at cs.uiuc.edu); LLVM Developers Mailing List (llvmdev at cs.uiuc.edu) Subject: Re: [LLVMdev] [lldb-dev] [cfe-dev] What does "debugger tuning" mean? @Adrian, "I don't think there was a driver patch" actually yes there is, see below. @Eric, "Does the patch do all of this?" Basically, yes, see http://reviews.llvm.org/D8506 The target-based default for the tuning parameter is done by code at the top of...

...wine --debugmsg fixme-font d:\\install.exe Invoking /opt/wine/bin/wine.bin --debugmsg fixme-font d:\install.exe ... /usr/bin/wine: mktemp: command not found /usr/bin/wine: mktemp: command not found Building font metrics. This may take some time... err:seh:UnhandledExceptionFilter Couldn't start debugger (debugger/winedbg 134631352 32) (2) Read the Wine Developers Guide on how to set up winedbg or another debugger Wine failed with return code 3 babylon5:alaric:~:47 $ ....But I don't WANT wine to start the debugger. As far as I can tell, Wine is now croaking because it's unable to sta...

Hi llvm-dev@, This is a proposal for LLVM to adopt Sony's Dexter tool [0], import it into the debuginfo-tests repo, and use it to run integration tests between debuggers and clang/llvms debuginfo. (Sony has approved donating Dexter to LLVM). Background ---------- The debuginfo-tests repo contains an integration test suite for debug data, which builds each test case from its source code using clang and runs the output in gdb/lldb, and for some the Windows-based c...

On Aug 17, 2007, at 4:17 PM, Fernando Magno Quintao Pereira wrote: > > Hi guys, > > I have been using a debugger for my register allocator. The > debugger > happened to be very useful at catching register assignment errors. > I've > put the debugger on-line, if anyone who is working with register > allocation wants to use. The debugger itself has nothing to do with > LLVM, > but...