Re: [ovs-dev] [PATCH 2/2] backtrace: Fix 32-bit libunwind build.

2019-10-09 Thread Alin Serdean
On 8 Oct 2019, at 20:51, Ben Pfaff mailto:b...@ovn.org>> wrote: On Tue, Oct 08, 2019 at 06:33:10PM +0200, Ilya Maximets wrote: On 08.10.2019 18:13, William Tu wrote: On Mon, Oct 07, 2019 at 07:10:26PM +0200, Ilya Maximets wrote: On 07.10.2019 18:11, Ilya Maximets wrote: On 07.10.2019 18:07, Wil

Re: [ovs-dev] [PATCH 2/2] backtrace: Fix 32-bit libunwind build.

2019-10-08 Thread Ben Pfaff
On Tue, Oct 08, 2019 at 06:33:10PM +0200, Ilya Maximets wrote: > On 08.10.2019 18:13, William Tu wrote: > > On Mon, Oct 07, 2019 at 07:10:26PM +0200, Ilya Maximets wrote: > > > On 07.10.2019 18:11, Ilya Maximets wrote: > > > > On 07.10.2019 18:07, William Tu wrote: > > > > > On Mon, Oct 7, 2019 at

Re: [ovs-dev] [PATCH 2/2] backtrace: Fix 32-bit libunwind build.

2019-10-08 Thread William Tu
On Tue, Oct 8, 2019 at 9:33 AM Ilya Maximets wrote: > > On 08.10.2019 18:13, William Tu wrote: > > On Mon, Oct 07, 2019 at 07:10:26PM +0200, Ilya Maximets wrote: > >> On 07.10.2019 18:11, Ilya Maximets wrote: > >>> On 07.10.2019 18:07, William Tu wrote: > On Mon, Oct 7, 2019 at 5:06 AM Ilya M

Re: [ovs-dev] [PATCH 2/2] backtrace: Fix 32-bit libunwind build.

2019-10-08 Thread Ilya Maximets
On 08.10.2019 18:13, William Tu wrote: On Mon, Oct 07, 2019 at 07:10:26PM +0200, Ilya Maximets wrote: On 07.10.2019 18:11, Ilya Maximets wrote: On 07.10.2019 18:07, William Tu wrote: On Mon, Oct 7, 2019 at 5:06 AM Ilya Maximets wrote: On 04.10.2019 23:21, William Tu wrote: The libunwind un

Re: [ovs-dev] [PATCH 2/2] backtrace: Fix 32-bit libunwind build.

2019-10-08 Thread William Tu
On Mon, Oct 07, 2019 at 07:10:26PM +0200, Ilya Maximets wrote: > On 07.10.2019 18:11, Ilya Maximets wrote: > >On 07.10.2019 18:07, William Tu wrote: > >>On Mon, Oct 7, 2019 at 5:06 AM Ilya Maximets wrote: > >>> > >>>On 04.10.2019 23:21, William Tu wrote: > The libunwind unw_word_t type is defi

Re: [ovs-dev] [PATCH 2/2] backtrace: Fix 32-bit libunwind build.

2019-10-07 Thread Ilya Maximets
On 07.10.2019 18:11, Ilya Maximets wrote: On 07.10.2019 18:07, William Tu wrote: On Mon, Oct 7, 2019 at 5:06 AM Ilya Maximets wrote: On 04.10.2019 23:21, William Tu wrote: The libunwind unw_word_t type is defined as uint32_t for 32-bit system and uint64_t for 64-bit system.  The patch fixes

Re: [ovs-dev] [PATCH 2/2] backtrace: Fix 32-bit libunwind build.

2019-10-07 Thread Ilya Maximets
On 07.10.2019 18:07, William Tu wrote: On Mon, Oct 7, 2019 at 5:06 AM Ilya Maximets wrote: On 04.10.2019 23:21, William Tu wrote: The libunwind unw_word_t type is defined as uint32_t for 32-bit system and uint64_t for 64-bit system. The patch fixes the compile error using PRIxPTR to print th

Re: [ovs-dev] [PATCH 2/2] backtrace: Fix 32-bit libunwind build.

2019-10-07 Thread William Tu
On Mon, Oct 7, 2019 at 5:06 AM Ilya Maximets wrote: > > On 04.10.2019 23:21, William Tu wrote: > > The libunwind unw_word_t type is defined as uint32_t for 32-bit > > system and uint64_t for 64-bit system. The patch fixes the > > compile error using PRIxPTR to print this value. > > > > Fixes: e2e

Re: [ovs-dev] [PATCH 2/2] backtrace: Fix 32-bit libunwind build.

2019-10-07 Thread Ilya Maximets
On 04.10.2019 23:21, William Tu wrote: The libunwind unw_word_t type is defined as uint32_t for 32-bit system and uint64_t for 64-bit system. The patch fixes the compile error using PRIxPTR to print this value. Fixes: e2ed6fbeb18c ("fatal-signal: Catch SIGSEGV and print backtrace.") Signed-off-

[ovs-dev] [PATCH 2/2] backtrace: Fix 32-bit libunwind build.

2019-10-04 Thread William Tu
The libunwind unw_word_t type is defined as uint32_t for 32-bit system and uint64_t for 64-bit system. The patch fixes the compile error using PRIxPTR to print this value. Fixes: e2ed6fbeb18c ("fatal-signal: Catch SIGSEGV and print backtrace.") Signed-off-by: William Tu Acked-by: Ilya Maximets