Displaying 8 results from an estimated 8 matches for "_unwind_getip".
2010 Feb 20
1
[LLVMdev] Generating a backtrace
...on backtrace information is actually
going to be used.
Within the personality function, there's a call to _Unwind_Backtrace(),
which walks through the list of call frames and calls a callback for each
one. Within the callback, I can get the value of the return address for each
call frame using _Unwind_GetIP(). So far so good.
The problem is converting those addresses into meaningful symbols. For some
reason that I don't understand, dladdr() doesn't seem to work on
LLVM-generated functions, even though I know those functions have full DWARF
debugging information. If I insert a printf into my b...
2007 Dec 08
4
[LLVMdev] Darwin vs exceptions
...ays):
Index: gcc/unwind-dw2.c
===================================================================
--- gcc/unwind-dw2.c (revision 124749)
+++ gcc/unwind-dw2.c (working copy)
@@ -1526,7 +1526,7 @@
static inline _Unwind_Ptr
uw_identify_context (struct _Unwind_Context *context)
{
- return _Unwind_GetIP (context);
+ return _Unwind_GetCFA (context);
}
I'm uncertain of the merit of this patch, but it's in shipping Leopard
and works with gcc, so we're
stuck with it.
The effect of this is that llvm's strategy of making every C++
selector claim that it has a catch-all
handler a...
2007 Dec 08
0
[LLVMdev] Darwin vs exceptions
...==================================================================
> --- gcc/unwind-dw2.c (revision 124749)
> +++ gcc/unwind-dw2.c (working copy)
> @@ -1526,7 +1526,7 @@
> static inline _Unwind_Ptr
> uw_identify_context (struct _Unwind_Context *context)
> {
> - return _Unwind_GetIP (context);
> + return _Unwind_GetCFA (context);
> }
>
> I'm uncertain of the merit of this patch, but it's in shipping
> Leopard and works with gcc, so we're
> stuck with it.
Right, this is effectively part of the darwin ABI now.
> The effect of this is that l...
2020 Aug 15
5
Supporting libunwind on Windows 10 (32bit; 64bit) for MSVC and Clang
...t *context, int
index,
^
C:/Users/clang/libunwind/include\unwind.h:222:13: note: previous
declaration is here
extern void _Unwind_SetGR(struct _Unwind_Context *context, int index,
^
C:/Users/clang/libunwind/src/UnwindLevel1.c:495:29: warning: redeclaration
of '_Unwind_GetIP' should not add 'dllexport' attribute
[-Wdll-attribute-on-redeclaration]
_LIBUNWIND_EXPORT uintptr_t _Unwind_GetIP(struct _Unwind_Context *context) {
^
C:/Users/clang/libunwind/include\unwind.h:224:18: note: previous
declaration is here
extern uintptr_t _Unwi...
2009 Sep 18
1
[LLVMdev] Exception Handling Tables Question
On Sep 17, 2009, at 6:03 PM, Duncan Sands wrote:
> Hi Bill,
>
>>>> Yeah. The logic will need tweaking for sure. I'm also concerned
>>>> about the
>>>> _Unwind_resume() call. GCC emits a call site region for it in the
>>>> exception
>>>> table. We...kind of do that. It looks like it's being included in
>>>>
2020 Aug 15
5
Supporting libunwind on Windows 10 (32bit; 64bit) for MSVC and Clang
On Sat, Aug 15, 2020 at 8:39 PM Martin Storsjö <martin at martin.st> wrote:
> Hi,
>
>
> On Sat, 15 Aug 2020, Ivan Serdyuk wrote:
>
> > Just as Shoaib said, libunwind only is useful in environments
> > that use
> > the Itanium C++ ABI - there's really no use for it in an MSVC
> > context
> > (either using MSVC or
2017 Jan 23
2
undefined symbols during linking LLDB 4.0 RC1
...000000a2 GLIBC_2.2.5 printf
0000000000000000 DF *UND* 0000000000000090 GLIBC_2.2.5 fprintf
0000000000000000 DF *UND* 00000000000001de LIBXML2_2.4.30 xmlFreeDoc
0000000000000000 DF *UND* 0000000000002393 GLIBC_2.2.5 atan
0000000000000000 DF *UND* 0000000000000008 GCC_3.0 _Unwind_GetIP
0000000000000000 DF *UND* 0000000000000162 Base _ZNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEE6appendEmc
0000000000000000 DF *UND* 0000000000000082 GLIBC_2.2.5 pthread_mutex_unlock
0000000000000000 DF *UND* 0000000000000044 GLIBC_2.2.5 cfsetospeed
000000000...
2017 Jan 19
2
undefined symbols during linking LLDB 4.0 RC1
Hello, I update my building scripts to build LLVM 4.0 RC1 (with clang, lldb, libc++, libc++abi, lld) on CentOS 6 and I got a lot of undefined symbols during linking LLDB.
I'm using clang-3.9 and this configuration:
-DLLVM_TARGETS_TO_BUILD="X86"
-DCMAKE_BUILD_TYPE=Release
-DCMAKE_C_COMPILER=/usr/bin/clang
-DCMAKE_CXX_COMPILER=/usr/bin/clang++