similar to: [PATCH] D15965: Add support for dumping relocations in non-relocatable files

While trying to fix a bug where llvm-objdump isn't printing relocations retained with ld -emit-relocs in shared object or executables, it seems like there isn't a way to split printing dynamic relocations from non-dynamic relocations as with GNU objdump -r and -R. I was thinking of adding a function RelocationRef::isDynamic() and filtering them this way when printing. Since RelocationRef

On Wed, Feb 18, 2015 at 6:58 AM, Colin LeMahieu <colinl at codeaurora.org> wrote: > It might help after adding explicit types where needed and before adding > the opaque pointer type, to change all pointers to a single type in the > existing type system, i8* could work or maybe a weird type that would shake > out any issues like i99*. > I'm not sure this would help

Hi David, Sorry, I forget to attach the valgrind dump to this. I was not sure if my implementation was ok, so I wanted to ask if I've done something wrong first. Process terminating with default action of signal 11 (SIGSEGV) Access not within mapped region at address 0xB at 0x54F4516: llvm::object::COFFObjectFile::moveSectionNext(llvm::object::DataRefImpl&) const

On 8 December 2010 21:25, Colin Law <clanlaw-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> wrote: > I am using Rails 3.0.3, Ruby 1.9.2 with rvm on Ubunutu 10.04.  I > generated a new app by rails new testunicorn.  By default the Webrick > server runs ok.  In order to try Unicorn I uncommented gem ''unicorn'' > in Gemfile and did bundle install.  rails server still runs

I am using rvm installed on Ubuntu 10.04 as recommended in the rvm docs (including changes to .bashrc) and all is working well with several versions of Rails, and Ruby 1.8.7 and 1.9.2. If I run rvm use 1.9.2 it says Using /home/colinl/.rvm/gems/ruby-1.9.2-p0 and if I run rvm info It shows exactly what I would expect for 1.9.2 and I can start the rails server and all is well. The problem arises if

On Mon, Nov 5, 2012 at 5:17 PM, Eric Christopher <echristo at gmail.com> wrote: > For llvm-dwarfdump we need to handle relocations inside the debug info > sections in order to successfully dump the dwarf info including strings. > Nick sent out a partial patch that did this not too long ago and I've taken > it and gone in a bit of a different direction, but kept the same basic

For llvm-dwarfdump we need to handle relocations inside the debug info sections in order to successfully dump the dwarf info including strings. Nick sent out a partial patch that did this not too long ago and I've taken it and gone in a bit of a different direction, but kept the same basic architecture. In place of applying the relocations to the data we've read from disk I'm keeping

I had a working Rails setup using RVM on Ubuntu 11.10 with /home on a separate partition. I installed Ubuntu 12.04 (Alpha) on the root partition, leaving the home partition unchanged. I now find that some things don''t work, I think due to the fact that the system has been updated and versions of libraries have changed. For example I get: $ rails c

Hi everyone. We're interested in contributing a Hexagon assembler to MC and we're looking for comments on a good way to integrate the grammar in to the infrastructure. We rely on having a robust assembler because we have a large base of developers that write in assembly due to low power requirements for mobile devices. We put in some C-like concepts to make the syntax easier and this

Hi, The llvm-objdump tool at the moment disassembles ARM ELF binary but with lot of extra user supplied data * The triple supplied on the command line for tools has to be be correct (ARM, thumb etc) * The ELF file cannot have mix of ARM and thumb * There is no direct way of using it such as llvm-objdump -d elf_file. This works for architectures such as Hexagon, X86

Hi folks, I am trying to implement the C bindings API for DebugInfo::DWARF::DWARFDie. My goal is to have a C library that reads and parses DWARF debugging format (just like how llvm-dwarfdump does, but maybe more than just dumping debug info) I've started with creating C structure for DebugInfo::DWARF::DWARFContext which contains all DWARF DIEs in the object file. For this I used ```

Hi All, I see that llvm-readobj displays information similar to GNU readelf does except DWARF data. I also see llvm-dwarfdump dumps all DWARF data in user readable format. Is there a plan for readobj to incorporate similar options? This will make readobj more feature complete for reading objects similar to readelf. If this is not the plan, will llvm-dwarfdump be a tool that regular user

On Sun, Sep 22, 2013 at 9:43 PM, Shankar Easwaran <shankare at codeaurora.org>wrote: > Hi Eli, > > Slightly changed the example :- > > .section somedata > .Ltmpa: > .word 100 > .Ltmpb: > .word 60 > .Ltmpc: > .word 40 > .Ltmpd: > .word (.Ltmpa-.Ltmpb)-.Ltmpc > > The GNU assembler properly handles the above. > > $as -c x.s -o x.o >

Currently llvm-dwarfdump isn't very useful on ELF .o files because it doesn't apply relocations. nlewycky at ducttape:~$ llvm-dwarfdump helloworld.o | grep debug_str\\[ 0x0000000c: DW_AT_producer [DW_FORM_strp] ( .debug_str[0x00000000] = "clang version 3.2 (trunk 163034)") 0x00000012: DW_AT_name [DW_FORM_strp] ( .debug_str[0x00000000] = "clang version 3.2 (trunk

On Mon, Feb 16, 2015 at 3:53 PM, Chris Lattner <clattner at apple.com> wrote: > > On Feb 6, 2015, at 3:38 PM, David Blaikie <dblaikie at gmail.com> wrote: > > It's an idea been thrown around in a few different threads (including > Rafael's recent > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20141201/247285.html > and Chandler's

Author: rie Repository: /hg/zfs-crypto/gate Revision: 03313218730eac4d34c28c7ddc91858f0fe04c79 Log message: 6340814 ld.so.1 core dump with HWCAP relocatable object + updated statistics Files: update: usr/src/cmd/sgs/include/libld.h update: usr/src/cmd/sgs/libld/common/relocate.c update: usr/src/cmd/sgs/liblddbg/common/liblddbg.msg update: usr/src/cmd/sgs/liblddbg/common/statistics.c update:

"syslinux-bot for H. Peter Anvin" <hpa at zytor.com> on Wed, 2013/12/04 12:39: > Commit-ID: ef81a3ad54845ffb5ad62714cd62db4740ad5cff > Gitweb: > http://www.syslinux.org/commit/ef81a3ad54845ffb5ad62714cd62db4740ad5cff > Author: H. Peter Anvin <hpa at zytor.com> AuthorDate: Wed, 4 Dec 2013 > 12:35:09 -0800 Committer: H. Peter Anvin <hpa at zytor.com>

On 17/11/2014 08:45, Ady wrote: > The Slackware Documentation Project wiki also mentions > "CONFIG_RELOCATABLE" in: > <http://docs.slackware.com/howtos:slackware_admin:linux_kernel_options_f > or_uefi_and_elilo> I've seen this page a while age (of course... I'm a Slackware user) and now remember that I was a bit surprised because the kernel shipped in DVD

On 11/17/2014 12:55 AM, Didier Spaier wrote: > > So one more question: why can one boot with a GRUB EFI bootloader > but not with the SYSLINUX bootloader, using the same kernel? > > More accurately, I know why: because of the aforementioned patch, but > then, why is this test needed in SYSLINUX only? > Because Grub boots the kernel in a "hostile" way (not using

On 18/11/2014 18:55, H. Peter Anvin wrote: > On 11/17/2014 12:55 AM, Didier Spaier wrote: >> So one more question: why can one boot with a GRUB EFI bootloader >> but not with the SYSLINUX bootloader, using the same kernel? >> >> More accurately, I know why: because of the aforementioned patch, but >> then, why is this test needed in SYSLINUX only? >> >