Re: [PATCH v2] On ppc64le we HAVE_RELIABLE_STACKTRACE

2018-03-12 Thread Josh Poimboeuf
On Fri, Mar 09, 2018 at 05:47:18PM +0100, Torsten Duwe wrote: > On Thu, 8 Mar 2018 10:26:16 -0600 > Josh Poimboeuf wrote: > > > This doesn't seem to address some of my previous concerns: > > You're right. That discussion quickly headed towards objtool > and I forgot about

Re: [PATCH v2] On ppc64le we HAVE_RELIABLE_STACKTRACE

2018-03-12 Thread Josh Poimboeuf
On Fri, Mar 09, 2018 at 05:47:18PM +0100, Torsten Duwe wrote: > On Thu, 8 Mar 2018 10:26:16 -0600 > Josh Poimboeuf wrote: > > > This doesn't seem to address some of my previous concerns: > > You're right. That discussion quickly headed towards objtool > and I forgot about this one paragraph

Re: [PATCH v2] On ppc64le we HAVE_RELIABLE_STACKTRACE

2018-03-09 Thread Torsten Duwe
On Thu, 8 Mar 2018 10:26:16 -0600 Josh Poimboeuf wrote: > This doesn't seem to address some of my previous concerns: You're right. That discussion quickly headed towards objtool and I forgot about this one paragraph with the remarks. > - Bailing on interrupt/exception

Re: [PATCH v2] On ppc64le we HAVE_RELIABLE_STACKTRACE

2018-03-09 Thread Torsten Duwe
On Thu, 8 Mar 2018 10:26:16 -0600 Josh Poimboeuf wrote: > This doesn't seem to address some of my previous concerns: You're right. That discussion quickly headed towards objtool and I forgot about this one paragraph with the remarks. > - Bailing on interrupt/exception frames That is a good

Re: [PATCH v2] On ppc64le we HAVE_RELIABLE_STACKTRACE

2018-03-08 Thread Josh Poimboeuf
On Mon, Mar 05, 2018 at 05:49:28PM +0100, Torsten Duwe wrote: > The "Power Architecture 64-Bit ELF V2 ABI" says in section 2.3.2.3: > > [...] There are several rules that must be adhered to in order to ensure > reliable and consistent call chain backtracing: > > * Before a function calls any

Re: [PATCH v2] On ppc64le we HAVE_RELIABLE_STACKTRACE

2018-03-08 Thread Josh Poimboeuf
On Mon, Mar 05, 2018 at 05:49:28PM +0100, Torsten Duwe wrote: > The "Power Architecture 64-Bit ELF V2 ABI" says in section 2.3.2.3: > > [...] There are several rules that must be adhered to in order to ensure > reliable and consistent call chain backtracing: > > * Before a function calls any

Re: [PATCH v2] On ppc64le we HAVE_RELIABLE_STACKTRACE

2018-03-05 Thread Segher Boessenkool
On Mon, Mar 05, 2018 at 05:49:28PM +0100, Torsten Duwe wrote: > The "Power Architecture 64-Bit ELF V2 ABI" says in section 2.3.2.3: > > [...] There are several rules that must be adhered to in order to ensure > reliable and consistent call chain backtracing: > > * Before a function calls any

Re: [PATCH v2] On ppc64le we HAVE_RELIABLE_STACKTRACE

2018-03-05 Thread Segher Boessenkool
On Mon, Mar 05, 2018 at 05:49:28PM +0100, Torsten Duwe wrote: > The "Power Architecture 64-Bit ELF V2 ABI" says in section 2.3.2.3: > > [...] There are several rules that must be adhered to in order to ensure > reliable and consistent call chain backtracing: > > * Before a function calls any

[PATCH v2] On ppc64le we HAVE_RELIABLE_STACKTRACE

2018-03-05 Thread Torsten Duwe
The "Power Architecture 64-Bit ELF V2 ABI" says in section 2.3.2.3: [...] There are several rules that must be adhered to in order to ensure reliable and consistent call chain backtracing: * Before a function calls any other function, it shall establish its own stack frame, whose size shall be

[PATCH v2] On ppc64le we HAVE_RELIABLE_STACKTRACE

2018-03-05 Thread Torsten Duwe
The "Power Architecture 64-Bit ELF V2 ABI" says in section 2.3.2.3: [...] There are several rules that must be adhered to in order to ensure reliable and consistent call chain backtracing: * Before a function calls any other function, it shall establish its own stack frame, whose size shall be