Re: [Lldb-commits] [PATCH] D132624: [LLDB] Devirtualize coroutine promise types for `std::coroutine_handle`

2022-12-07 Thread Adrian Vogelsgesang via lldb-commits
Thank you for that hint, Jim! This infrastructure indeed looks very interesting for my use case. I will most likely use the HistoryThread class to represent the backtrace of the logical coroutine threads. Is my understanding correct, that `GetExtendedBacktraceThreads` only allows me to append

Re: [Lldb-commits] [PATCH] D132624: [LLDB] Devirtualize coroutine promise types for `std::coroutine_handle`

2022-08-26 Thread Jim Ingham via lldb-commits
> On Aug 26, 2022, at 5:08 PM, Adrian Vogelsgesang > wrote: > > Thank you for that hint, Jim! This infrastructure indeed looks very > interesting for my use case. > I will most likely use the HistoryThread class to represent the backtrace of > the logical coroutine threads. > > Is my

Re: [Lldb-commits] [PATCH] D132624: [LLDB] Devirtualize coroutine promise types for `std::coroutine_handle`

2022-08-26 Thread Jim Ingham via lldb-commits
> On Aug 26, 2022, at 7:05 AM, Adrian Vogelsgesang via Phabricator via > lldb-commits wrote: > > avogelsgesang added a comment. > >> I don't know much about coroutines, but it seems like your goal is to format >> them like a linked list > > actually, my preferred goal would be to show them

Re: [Lldb-commits] [PATCH] D132624: [LLDB] Devirtualize coroutine promise types for `std::coroutine_handle`

2022-08-25 Thread Jim Ingham via lldb-commits
> On Aug 25, 2022, at 8:11 AM, Pavel Labath via Phabricator via lldb-commits > wrote: > > labath added a comment. > > In D132624#3748434 , @avogelsgesang > wrote: > >>> The only concern is that if it would be not so easy to read if there are >>>