libunwind-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libunwind-devel] [PATCHv3 1/4] Add core dump unwinding support to l


From: Arun Sharma
Subject: Re: [Libunwind-devel] [PATCHv3 1/4] Add core dump unwinding support to libunwind
Date: Sat, 24 Mar 2012 15:31:50 -0700

On Fri, Mar 16, 2012 at 5:53 AM, Denys Vlasenko <address@hidden> wrote:

> I want this code to end up in libunwind.so instead,
> so we can use it equally from both libs.
>
> Our predicament seems to be that we have no good
> place to put its source in the source tree, right?
>
> drwxr-xr-x. 2 root root  4096 Feb 13 18:43 arm
> drwxr-xr-x. 2 root root  4096 Feb 13 18:43 hppa
> drwxr-xr-x. 2 root root  4096 Feb 13 18:43 ia64
> drwxr-xr-x. 2 root root  4096 Feb 13 18:43 mi
> drwxr-xr-x. 2 root root  4096 Feb 13 18:43 mips
> drwxr-xr-x. 2 root root  4096 Feb 13 18:43 ppc
> drwxr-xr-x. 2 root root  4096 Feb 13 18:43 ppc32
> drwxr-xr-x. 2 root root  4096 Feb 13 18:43 ppc64
> drwxr-xr-x. 2 root root  4096 Feb 13 18:43 x86
> drwxr-xr-x. 2 root root  4096 Feb 13 18:43 x86_64
>
> The above dirs are arch specific - not suitable.

The code is also ia64 specific. I don't have any objections to putting
it under ia64.

> drwxr-xr-x. 2 root root  4096 Feb 13 18:43 unwind
>
> Can we put it into this dir?

That dir is for C++ ABI support. We shouldn't move it there.

Re: common

There is also a dir called "mi" (machine independent). But this is
arch specific code, so we shouldn't move it there.

If runtime dependency between different components of libunwind*.a is
a concern, you can statically link object files into
libunwind-coredump.a with some Makefile hackery.

 -Arun



reply via email to

[Prev in Thread] Current Thread [Next in Thread]