similar to: GDB pretty printers for LLVM ADTs

Added some basic DenseMap support in r290011 On Fri, Dec 16, 2016 at 2:05 PM David Blaikie <dblaikie at gmail.com> wrote: > I've added a few LLVM GDB pretty printers a while back (& just added > llvm::Optional earlier today) & thought people might be interested in how > to use them, etc. > > I use them by adding the following to my .gdbinit: > > source

Excellent. I think it would make sense to add small section somewhere in documentation (e.g. LLVM Programmer’s Manual <http://llvm.org/docs/ProgrammersManual.html>) about it, so it won't be lost somewhere in the mailing list. Piotr 2016-12-17 1:04 GMT+01:00 David Blaikie via llvm-dev < llvm-dev at lists.llvm.org>: > Added some basic DenseMap support in r290011 > > On

Good point - any ideas on where in the programmer's manual would suit best? Looking around I sort of feel like it belongs in the "Picking the right data structure" section - but I fear someone merely examining existing data structures might not think to look there for help in their task (if they have no need to 'pick' a data structure for a new use, etc). On Mon, Dec 19,

I guess adding section "Debugging" at the bottom of programmers manual would sounds like a good plan to me. Piotr 2016-12-20 6:03 GMT+01:00 David Blaikie <dblaikie at gmail.com>: > Good point - any ideas on where in the programmer's manual would suit > best? Looking around I sort of feel like it belongs in the "Picking the > right data structure" section -

Added something in r290186. Say, Reid - do you know anything about the MSVC formatters that are also provided in LLVM? Perhaps you could add a brief bit of documentation about them, if they need an explicit wiring up (if they just come for free/automatically - might not be worth documenting, people will find it when they need it) or point this thread to someone who knows about them to provide

The VC visualizers are automatcially installed. 2016-12-20 19:45 GMT+02:00 David Blaikie via llvm-dev < llvm-dev at lists.llvm.org>: > Added something in r290186. > > Say, Reid - do you know anything about the MSVC formatters that are also > provided in LLVM? Perhaps you could add a brief bit of documentation about > them, if they need an explicit wiring up (if they just

Dandy :) I looked into ways to do this for the GDB visualizers - but was unable to come up with a totally automated solution, unfortunately. On Tue, Dec 20, 2016 at 9:51 AM Yaron Keren <yaron.keren at gmail.com> wrote: > The VC visualizers are automatcially installed. > > > 2016-12-20 19:45 GMT+02:00 David Blaikie via llvm-dev < > llvm-dev at lists.llvm.org>: >

> On Dec 20, 2016, at 9:55 AM, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Dandy :) > > I looked into ways to do this for the GDB visualizers - but was unable to come up with a totally automated solution, unfortunately. I've wanted the same. Best I could think of was to embed them (or a reference to them) in the binary for the debugger to look at.

In r271357 I've committed GDB pretty printer script for the following types - ArrayRef $1 = llvm::ArrayRef of length 3 = {1, 0, 7} - StringRef $2 = "foo\000bar" $3 = "fo" - SmallString $4 = "foo\000bar" - *SmallVector(Impl)* $5 = llvm::SmallVector of length 3, capacity 3 = {1, 0, 7} All of these visualizers are pretty simple, robust,

Hi all, Need your help. I added some debug information to my code according to Kaleidoscope-9 sample and got stuck with a GDB error: (gdb) info functions > invalid dwarf2 offset 1849950870 > My module is a DLL built with llc+ld toolchain. Target triple: 'i686-w64-mingw32'. Looking this offset (1849950870 == 0x6e440296) in dwarfdump output of the dll gave the following:

I was told that my writeup lacked an example and details so I reproduced the code that X uses and I was able to boil down the issue to a couple of lines of code. Sorry again for the length of this email. Code was compiled on OpenBSD with clang 3.0-release. ======================================================================== With -O0 which works as X expects:

Sorry, this is the attachment. 2014-02-19 15:08 GMT+08:00 杨勇勇 <triple.yang at gmail.com>: > Thank you. > > Here is an example and the attchment contains extra files including object > file and executable file. > I want to print for example the value of "a", but lldb command "frame > variable a" displays "0" and so does "b", and

hi guys! i have some problem whit wine about the $SUBJECT i start my program and i get the following error message: ceta.2@sb-003:~/.wine/fakewin/csoft30 > wine --debugmsg +comm --managed comkern.exe err:win32:fixup_imports No implementation for shlwapi.dll.0(StrRetToBufA) imported from shell32.dll, setting to 0xdeadbeef err:win32:fixup_imports No implementation for

All of this information is contained in the DWARF debug info that you must generate. Are you generating DWARF? If not, you will need to. If so, please attach an example program that contains DWARF and specify which function you are having trouble getting variable information for. Greg Clayton On Feb 18, 2014, at 12:44 AM, 杨勇勇 <triple.yang at gmail.com> wrote: > Hi, all > > I

On Thu, Dec 15, 2016 at 11:35 AM Mehdi Amini <mehdi.amini at apple.com> wrote: > > > On Dec 15, 2016, at 10:54 AM, David Blaikie via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > Branching off from a discussion of improvements to DIGlobalVariable > representations that Adrian's working on - got me thinking about related > changes that have

Hi, all I ported llvm backend and lldb recently. Both tools can basically work. lldb is able to debug programs in asm style and frame unwinding is OK. But "frame variable XX" does not work because lldb is not able to determine the address of XX from debug info. Can someone give any clue? Thanks in advance. -- 杨勇勇 (Yang Yong-Yong) -------------- next part -------------- An HTML

Thanks to Rails developer team. I tried Rails3 along this guide: Ruby on Rails Guides: Getting Started with Rails http://edgeguides.rubyonrails.org/getting_started.html and I met the problem described as following. ...Any ideas? =========== Environment: =========== $ ruby -v ruby 1.8.7 (2010-08-16 patchlevel 302) [i686-darwin9.8.0] $ rails -v Rails 3.0.3 =========== Steps for reproduce:

I try to use SimoComU, a tool to control frequency converters, on Wine. Since version 2004-07-16 it opens its main window, and most functions seem to work. Anyway, it does not communicate over the serial line. I see the following output: trace:file:CreateFileW L"COM1" GENERIC_READ GENERIC_WRITE OPEN_EXISTING attributes 0x0 trace:file:RtlDosPathNameToNtPathName_U

Hi, I applied your patch and recompiled, but I'm still having trouble. In what follows I've tried to describe some details. The first problem was this: The Comm-Port gets opened with overlapped I/O. However, for WaitCommEvent() we do not specify an overlapped structure. This works fine on NT4 / W2K, but is contrary to the documentation, which specifys that you need to supply an

Hi all, I wanted to draw some attention to a couple of very small multibyte-related patches I believe should be included before Rails 3.0 RC1: * Use String#bytesize rather than String#length in exception templates: This is a simple case where string length is checked, but bytes is needed, so it breaks with string with multibyte chars.