On Wed, Sep 17, 2025 at 4:01 PM HAGIO KAZUHITO(萩尾 一仁)
wrote:
> On 2025/09/17 16:20, lijiang wrote:
> > On Wed, Sep 17, 2025 at 2:17 PM HAGIO KAZUHITO(萩尾 一仁)
> > mailto:k-hagio...@nec.com>> wrote:
> >
> > Hi Lianbo,
> >
> > Thank you for fixing it quickly.
> >
> > btw, seeing 99bb57ac9
On 2025/09/17 16:20, lijiang wrote:
> On Wed, Sep 17, 2025 at 2:17 PM HAGIO KAZUHITO(萩尾 一仁)
> mailto:k-hagio...@nec.com>> wrote:
>
> Hi Lianbo,
>
> Thank you for fixing it quickly.
>
> btw, seeing 99bb57ac98af, I had a couple of questions, is there a
> way to
> print the ori
On Wed, Sep 17, 2025 at 2:17 PM HAGIO KAZUHITO(萩尾 一仁)
wrote:
> Hi Lianbo,
>
> Thank you for fixing it quickly.
>
> btw, seeing 99bb57ac98af, I had a couple of questions, is there a way to
> print the original (not mangled) log buffer?
>
Good questions, Kazu.
Add an option(E.g -R) to the log com
Hi Lianbo,
Thank you for fixing it quickly.
btw, seeing 99bb57ac98af, I had a couple of questions, is there a way to
print the original (not mangled) log buffer?
also, if the log buffer has lines like "_R ... +" which are not rust
symbols unexpectedly, how are they printed?
(nice function, but
applied:
https://github.com/crash-utility/crash/commit/0df76345db8f7bb2ce70138eee65b71e157b280a
On Wed, Sep 17, 2025 at 10:34 AM Tao Liu wrote:
>
> Hi Lianbo,
>
> Thanks for the fix, LGTM, ack.
>
> Thanks,
> Tao Liu
>
> On Tue, Sep 16, 2025 at 8:05 PM Lianbo Jiang wrote:
> >
> > The log command
Hi Lianbo,
Thanks for the fix, LGTM, ack.
Thanks,
Tao Liu
On Tue, Sep 16, 2025 at 8:05 PM Lianbo Jiang wrote:
>
> The log command printed a couple of empty lines (only timestamps), which
> was caused by the commit 99bb57ac98af ("Enable resolving mangled Rust
> symbol in lockless ring buffer"),
