Re: [ovs-dev] [PATCH v5] backtrace: Extend the backtrace functionality

2023-05-30 Thread Ilya Maximets
On 5/30/23 09:34, Ales Musil wrote: > > > On Mon, May 29, 2023 at 7:15 PM Ilya Maximets > wrote: > > On 5/25/23 08:33, Ales Musil wrote: > > Use the backtrace functions that is provided by libc, > > this allows us to get backtrace that is independent of >

Re: [ovs-dev] [PATCH v5] backtrace: Extend the backtrace functionality

2023-05-30 Thread Ales Musil
On Mon, May 29, 2023 at 7:15 PM Ilya Maximets wrote: > On 5/25/23 08:33, Ales Musil wrote: > > Use the backtrace functions that is provided by libc, > > this allows us to get backtrace that is independent of > > the current memory map of the process. Which in turn can > > be used for

Re: [ovs-dev] [PATCH v5] backtrace: Extend the backtrace functionality

2023-05-29 Thread Ilya Maximets
On 5/25/23 08:33, Ales Musil wrote: > Use the backtrace functions that is provided by libc, > this allows us to get backtrace that is independent of > the current memory map of the process. Which in turn can > be used for debugging/tracing purpose. The backtrace > is not 100% accurate due to

[ovs-dev] [PATCH v5] backtrace: Extend the backtrace functionality

2023-05-25 Thread Ales Musil
Use the backtrace functions that is provided by libc, this allows us to get backtrace that is independent of the current memory map of the process. Which in turn can be used for debugging/tracing purpose. The backtrace is not 100% accurate due to various optimizations, most notably