search for: dwarfdump

I would like to grow llvm-dwarfdump to become a drop-in replacement for the dwarfdump utility that is currently shipping on Darwin. (You can search the web for "darwin dwarfdump manpage" to see the currently supported feature set.) Doing this means implementing the missing features, such as the ability to print only subsets...

******************** FAIL: LLVM :: tools/llvm-dwarfdump/X86/debug-names-find.s (38881 of 41794) ******************** TEST 'LLVM :: tools/llvm-dwarfdump/X86/debug-names-find.s' FAILED ******************** Script: -- /home/csabaraduly/wk/LLVM/build_release/bin/llvm-mc -triple x86_64-pc-linux /home/csabaraduly/wk/LLVM/llvm/test/tools/llvm-dwarfdump...

Hello Csaba, Thanks for the heads up. I am the one who wrote that test. I'll look into that shortly. Sorry about the trouble. pl On Mon, 16 Apr 2018 at 11:56, Csaba Raduly via llvm-dev < llvm-dev at lists.llvm.org> wrote: > ******************** > FAIL: LLVM :: tools/llvm-dwarfdump/X86/debug-names-find.s (38881 of 41794) > ******************** TEST 'LLVM :: > tools/llvm-dwarfdump/X86/debug-names-find.s' FAILED > ******************** > Script: > -- > /home/csabaraduly/wk/LLVM/build_release/bin/llvm-mc -triple > x86_64-pc-linux /home/csabaraduly/wk...

...for the heads up. I am the one who wrote that test. I'll look into > that shortly. Sorry about the trouble. > pl > On Mon, 16 Apr 2018 at 11:56, Csaba Raduly via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > ******************** > > FAIL: LLVM :: tools/llvm-dwarfdump/X86/debug-names-find.s (38881 of 41794) > > ******************** TEST 'LLVM :: > > tools/llvm-dwarfdump/X86/debug-names-find.s' FAILED > > ******************** > > Script: > > -- > > /home/csabaraduly/wk/LLVM/build_release/bin/llvm-mc -triple > > x8...

...CBug.ll [ 1553s] LLVM :: CodeGen/PowerPC/available-externally.ll [ 1553s] LLVM :: CodeGen/PowerPC/branch-opt.ll [ 1553s] LLVM :: CodeGen/PowerPC/stubs.ll [ 1553s] LLVM :: DebugInfo/debuglineinfo.test [ 1553s] LLVM :: DebugInfo/dwarf-public-names.ll [ 1553s] LLVM :: DebugInfo/dwarfdump-debug-frame-simple.test [ 1553s] LLVM :: DebugInfo/dwarfdump-inlining.test [ 1553s] LLVM :: DebugInfo/dwarfdump-pubnames.test [ 1553s] LLVM :: DebugInfo/dwarfdump-test.test [ 1553s] LLVM :: DebugInfo/dwarfdump-zlib.test [ 1553s] LLVM :: DebugInfo/llvm-symbolizer.test [ 1553s]...

Nick, Do you happen to know why the version reported in 'dwarfdump --eh-frame' for object files now differs when compiled with and without -g? The test used in FSF gcc's configure produces a diff of.. % diff -u conftest.o.g.stripped.dwarfdump conftest.o.g0.stripped.dwarfdump --- conftest.o.g.stripped.dwarfdump 2015-04-10 21:43:15.000000000 -0400 +++ conft...

On Fri, Sep 8, 2017 at 2:32 PM, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > On Fri, Sep 8, 2017 at 2:25 PM Adrian Prantl <aprantl at apple.com> wrote: >> >> I would like to grow llvm-dwarfdump to become a drop-in replacement for >> the dwarfdump utility that is currently shipping on Darwin. (You can search >> the web for "darwin dwarfdump manpage" to see the currently supported >> feature set.) > > > For anyone looking: http://www.manpagez.com/man/1/d...

On Feb 11, 2013, at 18:13, Eli Bendersky <eliben at google.com> wrote: > On Thu, Feb 7, 2013 at 2:50 PM, Erik Verbruggen <erikjv at me.com> wrote: >> Hi, >> >> I noticed that llvm-dwarfdump does not show any information about the eh_frame section. While DWARFContext::getDebugAranges explicitly tries to parse it, it fails because the DWARFContextInMemory constructor does not check for that specific section name. A fix would be to check wether the name is "debug_frame" or &quo...

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 can use and rely on or it is on...

Hi, [ I think I put the most important contributors to the DebugInfo stuff in Cc:. Is there anyone else that I am missing? ] Just a short notice that I am currently working on making llvm-dwarfdump more developer friendly. There are quite a few features in Darwin’s dwarfdump that we find quite useful and that we would like to contribute to llvm-dwarfdump. I have started by augmenting the -debug-dump=info output: - Symbolic names for attribute values - Line table lookups for DW_AT_decl_file...

...ent kinds of version LLVM? If not, I may try to download and compile the newest version of llvm and compile the specific binaries. Could you try reducing this test further? Taking the code/compile commands and try to reduce the remove anything in the source code that isn't needed to cause llvm-dwarfdump to crash? ============================= I may not be able to reduce it. CPU SPEC is the standard benchmark and I am not very familiar to the source code. The target binary is also rather large. Sorry for that. Regards Muhui David Blaikie <dblaikie at gmail.com> 于2018年11月4日周日 上午4:02写道： &g...

Hi I come across the following exception when I use the llvm-dwarfdump -debug-info target_binary: llvm-dwarfdump: /home/linux/llvm-7/llvm/lib/MC/MCRegisterInfo.cpp:87: int llvm::MCRegisterInfo::getLLVMRegNum(unsigned int, bool) const: Assertion `I != M+Size && I->FromReg == RegNum && "Invalid RegNum"' failed. Stack dump: 0. Progr...

>> > I'm fine with this as long as llvm-dwarfdump gets maintained. >> > >> >> I agree, and as I said in the original email, in the long term I >> believe llvm-dwarfdump is the correct solution. >> > > The problem is that if no one is working on testing these sorts of things > with llvm-dwarfdump then it wo...

Hi, I noticed that llvm-dwarfdump does not show any information about the eh_frame section. While DWARFContext::getDebugAranges explicitly tries to parse it, it fails because the DWARFContextInMemory constructor does not check for that specific section name. A fix would be to check wether the name is "debug_frame" or &quo...

...g. Regards Muhui David Blaikie <dblaikie at gmail.com> 于2018年11月4日周日 上午2:58写道： > > > On Sat, Nov 3, 2018 at 6:51 AM Muhui Jiang via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi >> >> I come across the following exception when I use the llvm-dwarfdump >> -debug-info target_binary: >> >> llvm-dwarfdump: /home/linux/llvm-7/llvm/lib/MC/MCRegisterInfo.cpp:87: int >> llvm::MCRegisterInfo::getLLVMRegNum(unsigned int, bool) const: Assertion `I >> != M+Size && I->FromReg == RegNum && "Invalid RegNum&...

...ce! Alex. ________________________________ The clang-tidy cert-mem57 tests seem to be related to varying messages (warning|error) being emitted. All three MachO/gen-dwarf test are crashing at about the same place: Stack dump: 0. Program arguments: d:\llvm-project\buildninjarelmsvc\bin\llvm-dwarfdump.exe -all D:\llvm-project\buildninjaRelMSVC\test\MC\MachO\Output\gen-dwarf.s.tmp #0 0x00007ff6c125dfb8 llvm::DWARFCompileUnit::dump(class llvm::raw_ostream &, struct llvm::DIDumpOptions) D:\llvm-project\llvm\lib\DebugInfo\DWARF\DWARFCompileUnit.cpp:23:0 #1 0x00007ff6c1236e18 <lambda_25ce692e1...

On Thu, Feb 7, 2013 at 2:50 PM, Erik Verbruggen <erikjv at me.com> wrote: > Hi, > > I noticed that llvm-dwarfdump does not show any information about the eh_frame section. While DWARFContext::getDebugAranges explicitly tries to parse it, it fails because the DWARFContextInMemory constructor does not check for that specific section name. A fix would be to check wether the name is "debug_frame" or &quo...

On Mar 17, 2011, at 8:44 AM, Renato Golin wrote: >> dwarfdump --verify will do this. > > Is this being used in LLVM tests? This is an idea. It is not used in llvm/test tests. > I had a look at your debug tests in clang and they're similar to what I do here. > > The problem with debug tests is that it doesn't depend only on the >...

On Fri, Jan 18, 2013 at 3:13 PM, Eli Bendersky <eliben at google.com> wrote: > >> > I'm fine with this as long as llvm-dwarfdump gets maintained. > >> > > >> > >> I agree, and as I said in the original email, in the long term I > >> believe llvm-dwarfdump is the correct solution. > >> > > > > The problem is that if no one is working on testing these sorts of things...

...:: CodeGen/PowerPC/available-externally.ll > [ 1553s] LLVM :: CodeGen/PowerPC/branch-opt.ll > [ 1553s] LLVM :: CodeGen/PowerPC/stubs.ll > [ 1553s] LLVM :: DebugInfo/debuglineinfo.test > [ 1553s] LLVM :: DebugInfo/dwarf-public-names.ll > [ 1553s] LLVM :: DebugInfo/dwarfdump-debug-frame-simple.test > [ 1553s] LLVM :: DebugInfo/dwarfdump-inlining.test > [ 1553s] LLVM :: DebugInfo/dwarfdump-pubnames.test > [ 1553s] LLVM :: DebugInfo/dwarfdump-test.test > [ 1553s] LLVM :: DebugInfo/dwarfdump-zlib.test > [ 1553s] LLVM :: DebugInfo/llvm-sy...