TiKV 4.0 Unable to Debug

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tikv4.0 无法debug

| username: TiDBer_uuJnGXxx

[TiDB Usage Environment]
Ubuntu 18, Rust 1.63.0, CLion 2022.2, GDB 8.1

[Issue] Current Problem
When using CLion to debug TiKV, the variable values cannot be seen, as shown in Figures 1 and 2. However, it works fine with a locally built Rust project.
If the package is specified as cmd during debugging, it cannot debug and reports that the Builder method is not implemented, as shown in Figure 3.

[Business Impact]
Unable to debug

[TiDB Version]
TiKV, PD, and TiDB are all release 4.0

[Application Software and Version]
Rust 1.63.0, CLion 2022.2, GDB 8.1

[Attachments] Relevant Logs and Configuration Information

4440da21096a0fe0578880fbf0b5d28
4440da21096a0fe0578880fbf0b5d281330×998 285 KB

b5afbaa824acada958e6b104595d019
b5afbaa824acada958e6b104595d0191330×998 287 KB

5b0c0bea3a287b711d63ce7a667c863
5b0c0bea3a287b711d63ce7a667c8631330×998 307 KB

  • TiUP Cluster Display Information
  • TiUP Cluster Edit Config Information

Monitoring (https://metricstool.pingcap.com/)

  • TiDB-Overview Grafana Monitoring
  • TiDB Grafana Monitoring
  • TiKV Grafana Monitoring
  • PD Grafana Monitoring
  • Corresponding Module Logs (including logs 1 hour before and after the issue)
2
| username: Billmay表妹 | Original post link

The issue has been identified: some parameters need to be changed in cargo build.

3
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.