similar to: [llvm] r263971 - [llvm-objdump] Printing relocations in executable and shared object files. This partially reverts r215844 by removing test objdump-reloc-shared.test which stated GNU objdump doesn't print relocations, it does.

It sounds like what you’re asking is, rather that universally calling RelocationRef::getOffset inside llvm-objdump.cpp I should: * Check if Obj “isRelocatableObject” * If it is, call RelocationRef::getOffset() * If it isn’t o Call RelocationRef::getAddress() o Build an ordered map of all sections and their bounds, check if the relocation lands within a section o

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

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

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

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

Hi, We are trying to use LLVM API to programmatically obtain a list of relocations in an ELF file. The way we are doing this is exactly as llvm-objdump does it: we are iterating through sections and in each section we are iterating over relocations (see PrintRelocations() function at https://llvm.org/svn/llvm-project/llvm/trunk/tools/llvm-objdump/llvm-objdump.cpp). However, it does not give us

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 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

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

Hello i see that the address of specific symbol are not the same between llvm-objdump and objdump. The code: --- #include <stdio.h> int machin = 42; int main () { printf("Hello : %d\n", machin); return 0; } ---- compile command: clang hello1.c -o hello1 And the address of the symbol of the global variable "machin": [ Fri Mar 08 - 22:58:36 ][ wwolff at hostname

Hello LLVM, Previously, some folks wanted llvm-objdump to behave more like GNU objdump. This could encompass both command line options and output format. Such a change helps developers already familiar with GNU tools and allows re-use of Perl scripts or other automation expecting to see GNU style dumps. Is moving llvm-objdump toward GNU objdump the general preference? And what about otools

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

Neo, On Oct 11, 2011, at 12:15 AM, Neo wrote: > 1. arm instruction decoder cannot recognise bx series instructions. Can you provide a testcase for an instruction it fails to disassemble? --Owen

Mac G4. The non-POD stuff was cleared out by Michael Spencer's refactoring of llmv-objdump. Thanks Michael! Now I just have to figure out how to get Debug+Asserts to build on Mac G4. Cheers, Joe Abbey Software Architect Arxan Technologies, Inc. 1305 Cumberland Ave, Ste 215 West Lafayette, IN 47906 W: 765-889-4756 x2 C: 765-464-9893 jabbey at arxan.com<mailto:jabbey at arxan.com>

I've made a change to llvm-objdump and feel uncomfortable checking it in without a test case. Where do the "make check" tests for tools like llvm-objdump go? Worse comes to worse, I'll stick it in test/MC/Mips since it is there I need the change for other Mips/MC tests. Thanks, Jack -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Mon, Aug 27, 2012 at 11:07 AM, Carter, Jack <jcarter at mips.com> wrote: > I've made a change to llvm-objdump and feel uncomfortable checking > it in without a test case. Where do the "make check" tests for tools like > llvm-objdump go? > > Worse comes to worse, I'll stick it in test/MC/Mips since it is there I need > the change for other Mips/MC tests.

hi, as of the moment, llvm-objdump fails on every archs, except x86, arm, aarch64, mips and some other "minor" archs. some notable ones are PPC, Sparc, .... this is due to the lack of support for disasm component of those archs in MC. any plan, roadmap, or anybody is thinking about fixing this? thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

> On Apr 28, 2020, at 9:03 AM, David Blaikie <dblaikie at gmail.com> wrote: > > What does llvm-dwarfdump tell you? > (particularly `--verify`) -- adrian