search for: gdbinit

...read_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir: $datadir/auto-load:/usr/bin/mono-gdb.py". To enable execution of this file add add-auto-load-safe-path /usr/lib64/libthread_db-1.0.so line to your configuration file "/home/andy/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/home/andy/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell:...

...s should be self explanatory. Patches and feedback welcome to add more visualizers, improve existing ones, etc. *How do you access/use these pretty printers?* Currently, the simplest thing to do is: source /path/to/your/llvm/src/utils/gdb-scripts/prettyprinters.py You can put this in your ~/.gdbinit if you want to make it more convenient. *Possible Usability Improvements* Just sourcing in .gdbinit doesn't scale if you have multiple LLVM source trees or debug builds that might be out of sync with one another (the ABI of the ADTs probably doesn't change all that often that this would b...

.... I want to set a breakpoint on malloc_error_break all the time (it makes no sense to re-run after setting the breakpoint on occasion). I want the breakpoint whenever the debugger starts, and for all projects (even projects that have not been created). Under GDB, I could probably do this via '.gdbinit.' It does not appear LLVM has the same as a search turned up no results (please correct me here). How can one set a permanent breakpoint on malloc_error_break under LLVM? Thanks in advance, Jeff

...oint on malloc_error_break > all the time (it makes no sense to re-run after setting the breakpoint > on occasion). I want the breakpoint whenever the debugger starts, and > for all projects (even projects that have not been created). > > Under GDB, I could probably do this via '.gdbinit.' It does not appear > LLVM has the same as a search turned up no results (please correct me > here). > > How can one set a permanent breakpoint on malloc_error_break under LLVM? Take a look at http://lldb.llvm.org/ for LLDB documentation. If you have further questions, this isn...

Hi Reed, On Jul 17, 2013, at 3:19 AM, Reed Kotler <rkotler at mips.com> wrote: > On 07/16/2013 06:01 PM, Reed Kotler wrote: >> The Eclipse indexer seems to get stuck in the Clang unittests/AST >> > > In Eclipse you can tell it that a given directory is derived, and then it won't try and index it. > > Probably the more complex clang tests are too involved

...my code for pretty printing for GDB for LLVM together with some infos on how to setup Eclipse for debugging here, if you want to give it a go: https://github.com/t-crest/patmos-llvm/tree/master/utils/gdb Basically, you need to check out the 'python' folder somewhere, check out the 'gdbinit' file, modify the paths to your system and make your gdb load the gdbinit file (beware, the Eclipse Standard Process launcher and the GDB (DSF) launcher seem to behave differently regarding whether they load the ~/.gdbinit file by default or not). Cheers, Stefan On 07/17/2013 10:43 AM,...

...give it R.binary, it does not have the wrapper stuff from Greg> R and crashes, If I give it R it complains because it is not a Greg> binary, and if I do R -d then I don't get the emacs extras. Make a symbolic link from your current directory to $RHOME/bin/R.binary then create a file .gdbinit in the current directory. Add the lines set env RHOME /usr/lib/R set env R_PAPERSIZE letter set env R_PRINTCMD lpr to the .gdbinit file. (Substitute your values for these variables.) At this point you can type M-x gdb <RET> R.binary <RET> to start a gdb session running R. If you...

...File "/lib64/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". To enable execution of this file add add-auto-load-safe-path /lib64/libthread_db-1.0.so line to your configuration file "/root/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/root/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell...

How can I debug code that I load at runtime? Currently I do the following: load R.binary into gdb run load shared object code using dyn.load() quit the R process from then on gdb seems to be smart enough such that the source code of the .so file is available and I can set breakpoints etc. however, when I restart the R process I get: (gdb) break printing.c:7 Breakpoint 1 at 0x407af036:

On 07/16/2013 06:01 PM, Reed Kotler wrote: > The Eclipse indexer seems to get stuck in the Clang unittests/AST > In Eclipse you can tell it that a given directory is derived, and then it won't try and index it. Probably the more complex clang tests are too involved for the indexer. >>> Hope this helps :) >>> >>> Regards, >>> >>> Tilmann

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 /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py Also, I can suggest adding: set print pretty on there too, it helps a lot when printing complex nested data structures. Once you have that, you can get pretty output like this: (gdb) p Abbrev->AbbrDeclSets $1 = std::map with...

...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 /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py > > Also, I can suggest adding: > > set print pretty on > > there too, it helps a lot when printing complex nested data structures. > > Once you have that, you can get pretty output like this: > &...

...t;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 /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py >> >> Also, I can suggest adding: >> >> set print pretty on >> >> there too, it helps a lot when printing complex nested data structures. >> >> Once you have that, you...

...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 /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py > > Also, I can suggest adding: > > set print pretty on > > there too, it helps a lot when printing complex nested data structures. > > Once you have that, you can get pretty output like this: > &...

...nueabihf/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". To enable execution of this file add add-auto-load-safe-path /lib/arm-linux-gnueabihf/libthread_db-1.0.so line to your configuration file "//.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "//.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: in...

...laikie 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 /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py >> >> Also, I can suggest adding: >> >> set print pretty on >> >> there too, it helps a lot when printing complex nested data structures. >> >> Once you have that, you...

...u suggested again, and there was a warning from the package manager about a cycle detected, but now gdb starts with the following messages... Traceback (most recent call last): File "<string>", ine 3, in <module> ModuleNotFoundError: No module named 'libstdcxx' /etc/gdbinit:5: Error in sourced command file: Error while executing Python code. There is also a line... This GDB was configured as "x86_64_pc-msys". (Shouldn't that be msys2?) If I ignore the messages and try to debug a terminal application, there are messages stating that multiple threads a...

...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 /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py > > Also, I can suggest adding: > > set print pretty on > > there too, it helps a lot when printing complex nested data structures. > > Once you have that, you can get pretty output like this: > &...

...laikie 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 /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py >> >> Also, I can suggest adding: >> >> set print pretty on >> >> there too, it helps a lot when printing complex nested data structures. >> >> Once you have that, you...

...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 /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py > > Also, I can suggest adding: > > set print pretty on > > there too, it helps a lot when printing complex nested data structures. > > Once you have that, you can get pretty output like this: > &...