search for: dwarf2

i'm evaluating an emulator for xeon, but it only supports dwarf2, not stabs. Is there a simple means of changing the config for the system gcc, or is this a much more involved thing? This is for releng_4. e.g. is loader, gdb -k, etc, all ok with seeing dwarf2 debugging info in /kernel, and in modules. --don

...e6bc) 9 0xb7d62ef8 GLIBC_2+0xef8 in libdl.so.2 (0xb7d62ef8) 10 0xb7fc67d6 _dl_catch_error+0x76 in ld-linux.so.2 (0xb7fc67d6) 11 0xb7d632f6 in libdl.so.2 (+0x12f6) (0xb7d632f6) 12 0xb7d62f44 GLIBC_2+0xf44 in libdl.so.2 (0xb7d62f44) fixme:dbghelp:elf_load_debug_info_from_map Alpha-support for Dwarf2 information for libwine.so.1 13 0xb7eb08bf wine_dlopen+0x2f(filename=0x7eb8b9f4, flag=0x102, error=0x0, errorsize=0x0) [loader.c:691] in libwine.so.1 (0xb7eb08bf) 6 0x6024624e in libc.so.6 (+0x10924e) (0x6024624e) 7 0x6000a7d6 _dl_catch_error+0x76 in ld-linux.so.2 (0x6000a7d6) 8 0x602466bc...

...le -fasynchronous-unwind-tables unless configured with --enable-frame-pointer. Enable -maccumulate-outgoing-args by default unless configured with --enable-frame-pointer. After testing on x86_64-appled-darwin10 and i386-apple-darwin10, I had the same enabled on darwin releases which default to dwarf2 now in FSF gcc trunk using... --- trunk/gcc/configure.ac 2010/08/13 15:50:40 163226 +++ trunk/gcc/configure.ac 2010/08/13 17:06:42 163227 @@ -1584,8 +1584,9 @@ [ --enable-frame-pointer enable -fno-omit-frame-pointer by default for 32bit x86], [], [ case $target_os in -linux*) - # Enable -fom...

...04041ce in yetisports7 (+0x41ce) (0x004041ce) 2 0x00404da3 in yetisports7 (+0x4da3) (0x00404da3) 3 0x7ff82c8d (0x7ff82c8d) 4 0x7ff8153e (0x7ff8153e) 5 0x7ff814e0 (0x7ff814e0) 6 0x7ffb0a68 (0x7ffb0a68) 7 0x7ffdf000 (0x7ffdf000) fixme:dbghelp:elf_load_debug_info_from_map Alpha-support for Dwarf2 information for kernel32<elf> 8 0x6039fe70 start_process+0xc0(arg=0x0) [/privat/emulator/wine/dlls/kernel/process.c:822] in kernel32 (0x6039fe70) fixme:dbghelp:elf_load_debug_info_from_map Alpha-support for Dwarf2 information for libwine.so.1 9 0x6001f527 wine_switch_to_stack+0x17 in l...

...a/arch/i386/lib/delay.c +++ b/arch/i386/lib/delay.c @@ -11,7 +11,6 @@ */ #include <linux/module.h> -#include <linux/config.h> #include <linux/sched.h> #include <linux/delay.h> =================================================================== --- a/include/asm-i386/dwarf2.h +++ b/include/asm-i386/dwarf2.h @@ -1,7 +1,5 @@ #ifndef _DWARF2_H #define _DWARF2_H - -#include <linux/config.h> #ifndef __ASSEMBLY__ #warning "asm/dwarf2.h should be only included in pure assembly files" =================================================================== --...

On Thu, Jun 26, 2014 at 3:39 PM, Robinson, Paul <Paul_Robinson at playstation.sony.com> wrote: > The main motivation for turning it off is that no known consumer (debugger) > took advantage of it. > > Turning it on does more than slightly increase the object file size, it can > cause the same source line to be listed multiple times in the .debug_line > table (with different

...x33e35c,0x33e35a fixme:uniscribe:ScriptApplyDigitSubstitution 0x621341ec,0x33f0c0,0x33f0be fixme:uniscribe:ScriptApplyDigitSubstitution 0x621341ec,0x33f1b4,0x33f1b2 fixme:uniscribe:ScriptApplyDigitSubstitution 0x621341ec,0x33f0a0,0x33f09e fixme:dbghelp:elf_load_debug_info_from_map Alpha-support for Dwarf2 information for xlcutf8load.so.2 err:win:DefWindowProcW called for other process window 0x10020 fixme:dbghelp:elf_load_debug_info_from_map Alpha-support for Dwarf2 information for ximcp.so.2 fixme:dbghelp_dwarf:dwarf2_compute_location Unhandled attr op: 75 fixme:uniscribe:ScriptApplyDigitSubstituti...

...t to prevent R_X86_64_32 generation? for 32bit dwarf, > I think generation of R_X86_64_32 is reasonable. > > you can check http://dwarfstd.org/doc/DWARF4.pdf. Because R_X86_64_32 elements are 4-byte addresses and can't be relocated for the 64-bit address space over 32-bit limit. Dwarf2 actually allows for both 32bit and 64-bit relocations. The document, mentioned by you, explains this in section 7.5.1.1 on page 143. If the first DWORD of .debug_info section is 0xffffffff, then this is 64-bit format. But LLVM for some reason always chooses DWARF 32-bit format. This is why I a...

...eNoImpersonate not handled wine: Unhandled page fault | on read access to 0x00000204 at address 0x7e70dc7d (thread 001d), starting | debugger... Unhandled exception: page fault on read access to 0x00000204 | in 32-bit code (0x7e70dc7d). fixme:dbghelp:elf_load_debug_info_from_map | Alpha-support for Dwarf2 information for oleaut32<elf> | fixme:dbghelp_dwarf:dwarf2_compute_location Only supporting one reg (0 -> | 2) fixme:dbghelp_dwarf:dwarf2_compute_location Only supporting one reg (0 | -> 2) fixme:dbghelp_dwarf:dwarf2_compute_location Only supporting one reg | (0 -> 2) fixme:dbghelp_d...

...ate from outside the function. Alternatively, passing in the compile unit makes sense, except that now there's no way to tell the IRBuilder about regions. Also, even though my code now assembles correctly, gdb gets very unhappy when I try to debug it - it prints "/build/buildd/gdb-7.0/gdb/dwarf2-frame.c:983: internal-error: Unknown CFA rule." and then asks me if I want to generate a core file of gdb. -- -- Talin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20091201/fddd03f4/attachment.html&gt...

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: 0x00000296: DW_TAG_base_type [10] DW_AT_name [DW_FORM_strp] ( .d...

...n either > i386-apple-darwin10 or x86_64-apple-darwin10, there are still some concerns > about the origins of the original Mach-O comment above. There also was > a concern that -fomit-frame-pointer would break Shark but my testing in > darwin10 suggests it still can profile code via the dwarf2. Thanks in > advance for any clarifications on the reasoning behind the original code. That's a long time ago :) At the time we needed to use the frame pointer instead of the eh frame information. If it works for you now I don't see any harm in turning it on. -eric

Hi, I have a newbie question regarding debugging support in llvm. Is llvm generating DWARF2 or DWARF3? The comments in the trunk source code refer to the DWARF 3 spec, but DWARF_VERSION is set to 2 in Support/Dwarf.h. What am I missing? Thanks. -- Yuan ----------------------------------------------------------------------------------- This email message is for the sole use of the in...

In your sequences in asm/paravirt.h, you explicitly save the caller-save regs: static inline void raw_local_irq_restore(unsigned long f) { __asm__ __volatile__(paravirt_alt("pushl %%ecx; pushl %%edx\n\t" "pushl %1; call *%0\n\t" "popl %1; popl %%edx; popl %%ecx", PARAVIRT_RESTORE_FLAGS) : : "m" (paravirt_ops.restore_fl),

On Wed, Nov 26, 2014 at 10:15:13AM +0000, Daniel Sanders wrote: > > From: Daniel Sanders > > Sent: 25 November 2014 17:39 > > To: Eric Christopher; Tom Stellard > > Cc: LLVM Developers Mailing List (llvmdev at cs.uiuc.edu) > > Subject: RE: [LLVMdev] Proposed patches for Clang 3.5.1 > > > > > > > > I'd also like to propose the inclusion of

...2c0 [ 0.684285] [<ffffffff81f56668>] prepare_namespace+0x12b/0x161 [ 0.686439] [<ffffffff81f56103>] kernel_init_freeable+0x1f6/0x20a [ 0.688675] [<ffffffff816c727a>] kernel_init+0xa/0x100 [ 0.690623] [<ffffffff816d485f>] ret_from_fork+0x1f/0x40 [ 0.696659] DWARF2 unwinder stuck at ret_from_fork+0x1f/0x40 [ 0.698858] [ 0.699533] Leftover inexact backtrace: [ 0.699533] [ 0.701580] [<ffffffff816c7270>] ? rest_init+0x90/0x90 [ 0.703944] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)

I have an application ("The Rosetta Stone" 2.0.7a) which segfaults during the startup splash screen. According to strace() it is trying to munmap() an address (0x7a6b3000) which was never mmap()'d. I get identical behavior with Wine 20050111 and kernels 2.6.9 / 2.6.10 (I use gentoo-sources). I noticed some people had similar issues upgrading from 2.6.9 to 2.6.10.

...г., в 5:35, Madhur Amilkanthwar <madhur13490 at gmail.com<mailto:madhur13490 at gmail.com>> написал(а): I don't understand the use case and reasons to blame PTXAS compiler here. >>a) Supports DWARF-2 only. What would you like to achieve with DWARF-3+ that you cannot do with DWARF2? >> b) Labels are allowed only in code section (only in functions). What is the use case here which needs labels outside functions? >>>c) Does not support label arithmetic in DWARF sections. Same. Please explain use case. d) Debug info must point to the sections, not to labels ins...

..., a memory error detector ==29007== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==29007== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info ==29007== Command: /usr/local/lib64/R-2.15.0-vg2/lib64/R/bin/exec/R --vanilla ==29007== --29007-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x2a valgrind: m_debuginfo/readdwarf.c:2292 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed. ==29007== at 0x3802B1F7: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) sched status: running_tid...

...llvm.org/pipermail/llvm-dev/2020-November/146673.html detailed why I don't like the conceptual model: the behavior is dependent on other sections. I also felt bad as I had to do string comparison on ".debug_" (https://reviews.llvm.org/D91404) I've chatted with gdb folks: gdb (gdb/dwarf2/read.c) is agnostic about the section type. (They just cannot handle multiple .debug_info sections.) SHT_PROGBITS is a default (or "use this if nothing more specific exists") section type that probably no tool will specifically check the type. For many tools, they don't understand DWA...