1:15 a.m.
Hi, PengFei
Thank you for the patch.
I can not apply your patch in my local repo, it seems some encoding issue
at my mail client. Can you help check your patch and
make sure that it's text/plain?
Thanks
Lianbo
On Wed, Jan 28, 2026 at 9:54 AM <devel-request(a)lists.crash-utility.osci.io>
wrote:
Date: Mon, 26 Jan 2026 10:02:48 +0000
From: 李鹏飞 <lipengfei28(a)xiaomi.com>
Subject: [Crash-utility] [PATCH] arm64: Fix broken/incomplete gdb
backtrace and unify output format
To: "devel(a)lists.crash-utility.osci.io"
<devel(a)lists.crash-utility.osci.io>
Cc: "anderson(a)redhat.com" <anderson(a)redhat.com>
Message-ID: <5db18509249d4a10a0b12a70b92a5a73(a)xiaomi.com>
Content-Type: multipart/alternative;
boundary="_000_5db18509249d4a10a0b12a70b92a5a73xiaomicom_"
--_000_5db18509249d4a10a0b12a70b92a5a73xiaomicom_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
RnJvbSA0ZDgzMmEzM2ViZDgwYmQxMDljYzVhNDdmOThjNmIzNWZkY2JkOTU2IE1vbiBTZXAgMTcg
MDA6MDA6MDAgMjAwMQ0KRnJvbTogbGlwZW5nZmVpMjggPGxpcGVuZ2ZlaTI4QHhpYW9taS5jb20+
DQpEYXRlOiBGcmksIDIzIEphbiAyMDI2IDE2OjI0OjA3ICswODAwDQpTdWJqZWN0OiBbUEFUQ0hd
ICBhcm02NDogRml4IGJyb2tlbi9pbmNvbXBsZXRlIGdkYiBiYWNrdHJhY2UgYW5kIHVuaWZ5IG91
dHB1dA0KZm9ybWF0DQoNClRoaXMgcGF0Y2ggZml4ZXMgbXVsdGlwbGUgaXNzdWVzIHdpdGggJ2dk
YiBidCcgb24gQVJNNjQsIHdoZXJlIHRoZSBiYWNrdHJhY2UNCndvdWxkIGJlIGludGVycnVwdGVk
LCBjb250YWluIGdhcmJhZ2UgdGhyZWFkcywgb3IgZGlzcGxheSBmcmFnbWVudGVkIG91dHB1dC4N
Cg0KMS4gRml4IE91dC1vZi1Cb3VuZHMgUmVhZCBpbiBFeGNlcHRpb24gRnJhbWUgSGFuZGxpbmc6
DQogICAgSW4gYGFybTY0X3ByaW50X2V4Y2VwdGlvbl9mcmFtZWAsIHRoZSBjb2RlIHByZXZpb3Vz
bHkgdXNlZCBgbWVtY3B5YCB0byBjb3B5DQogICAgYHNpemVvZihzdHJ1Y3QgYXJtNjRfcHRfcmVn
cylgIGJ5dGVzIGZyb20gYSBgc3RydWN0IGFybTY0X3N0YWNrZnJhbWUgKmAgc291cmNlLg0KICAg
IFNpbmNlIGBzdGFja2ZyYW1lYCBpcyBzaWduaWZpY2FudGx5IHNtYWxsZXIgdGhhbiBgcHRfcmVn
c2AsIHRoaXMgY2F1c2VkIGFuDQogICAgb3V0LW9mLWJvdW5kcyByZWFkLCBwb3B1bGF0aW5nIHRo
...
2:20 a.m.
New subject: 回复: [External Mail]Re: [PATCH] arm64: Fix broken/incomplete gdb backtrace and unify output format
Hi Lianbo,
Thanks for reviewing my patch.
Due to encoding issues with my enterprise email, the patch may appear garbled in some
clients.
To avoid this, I am sending the patch as a **UTF-8 plain text file attachment**.
Please find the patch attached. Let me know if there are any issues applying it locally,
or if you prefer another submission method.
Thanks again for your help!
Best regards,
Li Pengfei
发件人: lijiang <lijiang(a)redhat.com>
发送时间: 2026年1月30日 15:15
收件人: devel(a)lists.crash-utility.osci.io
抄送: 李鹏飞 <lipengfei28(a)xiaomi.com>
主题: [External Mail]Re: [PATCH] arm64: Fix broken/incomplete gdb backtrace and unify output
format
[外部邮件]
此邮件来源于小米公司外部，请谨慎处理。若对邮件安全性存疑，请将邮件转发给misec@xiaomi.com进行反馈<mailto:请将邮件转发给misec@xiaomi.com进行反馈>
Hi, PengFei
Thank you for the patch.
I can not apply your patch in my local repo, it seems some encoding issue at my mail
client. Can you help check your patch and
make sure that it's text/plain?
Thanks
Lianbo
On Wed, Jan 28, 2026 at 9:54 AM
<devel-request@lists.crash-utility.osci.io<mailto:devel-request@lists.crash-utility.osci.io>>
wrote:
Date: Mon, 26 Jan 2026 10:02:48 +0000
From: 李鹏飞 <lipengfei28@xiaomi.com<mailto:lipengfei28@xiaomi.com>>
Subject: [Crash-utility] [PATCH] arm64: Fix broken/incomplete gdb
backtrace and unify output format
To:
"devel@lists.crash-utility.osci.io<mailto:devel@lists.crash-utility.osci.io>"
<devel@lists.crash-utility.osci.io<mailto:devel@lists.crash-utility.osci.io>>
Cc: "anderson@redhat.com<mailto:anderson@redhat.com>"
<anderson@redhat.com<mailto:anderson@redhat.com>>
Message-ID:
<5db18509249d4a10a0b12a70b92a5a73@xiaomi.com<mailto:5db18509249d4a10a0b12a70b92a5a73@xiaomi.com>>
Content-Type: multipart/alternative;
boundary="_000_5db18509249d4a10a0b12a70b92a5a73xiaomicom_"
--_000_5db18509249d4a10a0b12a70b92a5a73xiaomicom_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
RnJvbSA0ZDgzMmEzM2ViZDgwYmQxMDljYzVhNDdmOThjNmIzNWZkY2JkOTU2IE1vbiBTZXAgMTcg
MDA6MDA6MDAgMjAwMQ0KRnJvbTogbGlwZW5nZmVpMjggPGxpcGVuZ2ZlaTI4QHhpYW9taS5jb20+
DQpEYXRlOiBGcmksIDIzIEphbiAyMDI2IDE2OjI0OjA3ICswODAwDQpTdWJqZWN0OiBbUEFUQ0hd
ICBhcm02NDogRml4IGJyb2tlbi9pbmNvbXBsZXRlIGdkYiBiYWNrdHJhY2UgYW5kIHVuaWZ5IG91
dHB1dA0KZm9ybWF0DQoNClRoaXMgcGF0Y2ggZml4ZXMgbXVsdGlwbGUgaXNzdWVzIHdpdGggJ2dk
YiBidCcgb24gQVJNNjQsIHdoZXJlIHRoZSBiYWNrdHJhY2UNCndvdWxkIGJlIGludGVycnVwdGVk
LCBjb250YWluIGdhcmJhZ2UgdGhyZWFkcywgb3IgZGlzcGxheSBmcmFnbWVudGVkIG91dHB1dC4N
Cg0KMS4gRml4IE91dC1vZi1Cb3VuZHMgUmVhZCBpbiBFeGNlcHRpb24gRnJhbWUgSGFuZGxpbmc6
DQogICAgSW4gYGFybTY0X3ByaW50X2V4Y2VwdGlvbl9mcmFtZWAsIHRoZSBjb2RlIHByZXZpb3Vz
bHkgdXNlZCBgbWVtY3B5YCB0byBjb3B5DQogICAgYHNpemVvZihzdHJ1Y3QgYXJtNjRfcHRfcmVn
cylgIGJ5dGVzIGZyb20gYSBgc3RydWN0IGFybTY0X3N0YWNrZnJhbWUgKmAgc291cmNlLg0KICAg
IFNpbmNlIGBzdGFja2ZyYW1lYCBpcyBzaWduaWZpY2FudGx5IHNtYWxsZXIgdGhhbiBgcHRfcmVn
c2AsIHRoaXMgY2F1c2VkIGFuDQogICAgb3V0LW9mLWJvdW5kcyByZWFkLCBwb3B1bGF0aW5nIHRo
...
#/******本邮件及其附件含有小米公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments contain confidential information from XIAOMI, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!******/#
3:19 a.m.
New subject: [PATCH] arm64: Fix broken/incomplete gdb backtrace and unify output format
On Fri, Jan 30, 2026 at 4:20 PM 李鹏飞 <lipengfei28(a)xiaomi.com> wrote:
Hi Lianbo,
Thanks for reviewing my patch.
Due to encoding issues with my enterprise email, the patch may appear
garbled in some clients.
To avoid this, I am sending the patch as a **UTF-8 plain text file
attachment**.
Please find the patch attached. Let me know if there are any issues
applying it locally, or if you prefer another submission method.
Thank you so much. It looks like plain text now.
I'll look at the patch in the coming weeks(maybe next week) and share my
thoughts with you.
Lianbo
Thanks again for your help!
Best regards,
Li Pengfei
68
days inactive
68
days old
devel@lists.crash-utility.osci.io
2 comments
2 participants
participants (2)
-
lijiang -
李鹏飞