Basic Common Sense
1. Any opinions can be discussed in
the group.
2. Don't be rude.
3. Please think independently.
4. Make sure your comments are understandable to you.
Tag Description
1. Release type: #PDB, #Experimental (for test only)
2. Ver naming convention: <mc-version>-<client/server>-<platform>
3. Symbols: refers to the total number of names recorded in PDB, the ratio is function with symbols/total functions (reference value: 1.21.3.01, 98.2%)
4. Types: refers to the total number of types recorded in PDB
5. CommitID: <DebugInfo Commit ID> & <Header Commit ID>
———————————————————
[ZH_CN]
基本常识
1. 任何意见可以加群讨论
2. 使用正常语言
3. 请独立思考
4. 确保你的言论可被自己理解（否则容易翻车）
标记说明
1. 发布类型: #PDB, #Experimental (仅供测试)
2. 版本号命名规则: <mc-version>-<client/server>-<platform>
3. 符号数量: 指记录在 PDB 中的名称总数，比率为有符号函数/总函数（参考值：1.21.3.01, 98.2%）
4. 类型数量: 指记录在 PDB 中的类型总数
5. 提交 ID: <DebugInfo工具链提交ID> & <Header提交ID>
1. Any opinions can be discussed in
the group.
2. Don't be rude.
3. Please think independently.
4. Make sure your comments are understandable to you.
Tag Description
1. Release type: #PDB, #Experimental (for test only)
2. Ver naming convention: <mc-version>-<client/server>-<platform>
3. Symbols: refers to the total number of names recorded in PDB, the ratio is function with symbols/total functions (reference value: 1.21.3.01, 98.2%)
4. Types: refers to the total number of types recorded in PDB
5. CommitID: <DebugInfo Commit ID> & <Header Commit ID>
———————————————————
[ZH_CN]
基本常识
1. 任何意见可以加群讨论
2. 使用正常语言
3. 请独立思考
4. 确保你的言论可被自己理解（否则容易翻车）
标记说明
1. 发布类型: #PDB, #Experimental (仅供测试)
2. 版本号命名规则: <mc-version>-<client/server>-<platform>
3. 符号数量: 指记录在 PDB 中的名称总数，比率为有符号函数/总函数（参考值：1.21.3.01, 98.2%）
4. 类型数量: 指记录在 PDB 中的类型总数
5. 提交 ID: <DebugInfo工具链提交ID> & <Header提交ID>
bedrock_server.pdb
66.4 MB
bedrock_server.pdb
63.8 MB
Open LiteLDev Notifications pinned «Basic Common Sense 1. Any opinions can be discussed in the group. 2. Don't be rude. 3. Please think independently. 4. Make sure your comments are understandable to you. Tag Description 1. Release type: #PDB, #Experimental (for test only) 2. Ver naming convention:…»
Today I’m happy to announce the release of DebugInfo v0.3.0!
For the past two weeks, my work has been focused on making the DebugInfo toolchain easier to use:
1. The project architecture is more reasonable: Now all implementations are concentrated in
2. Tools will provide truly useful error reports: The error handling model is now unified, so if the tool encounters an error while running, it will report context information and a stack trace instead of "saying nonsense" and exiting.
3. No longer rely on PreLoader released by LiteLDev: In the past, using PreLoader has been a problem, as it is not open source and does not run natively on Linux. Now there is support for built-in symbol resolvers, which are cross-platform and you no longer need to link to PreLoader.
4. Better documentation: In the last few days I have built a dedicated documentation site for DebugInfo (bedrockdebug.info) using mkdocs-material. It is very memorable because I want it to be immediately available when you need it. All the documentation has been rewritten (except for a small part that is waiting to be updated) and is much better and easier to understand than the original.
5. Create a Discord community: I recently learned that most people prefer to use Discord, so I created a server: https://discord.gg/fPKVZScPT7
DebugInfo is still under active development, and I plan to focus on mining more symbols to improve decompilation quality.
If you have any questions, please raise an issue, thanks everyone!!
For the past two weeks, my work has been focused on making the DebugInfo toolchain easier to use:
1. The project architecture is more reasonable: Now all implementations are concentrated in
libdi, and the tool provides TUI to call them, which will facilitate code sharing and secondary development.2. Tools will provide truly useful error reports: The error handling model is now unified, so if the tool encounters an error while running, it will report context information and a stack trace instead of "saying nonsense" and exiting.
3. No longer rely on PreLoader released by LiteLDev: In the past, using PreLoader has been a problem, as it is not open source and does not run natively on Linux. Now there is support for built-in symbol resolvers, which are cross-platform and you no longer need to link to PreLoader.
4. Better documentation: In the last few days I have built a dedicated documentation site for DebugInfo (bedrockdebug.info) using mkdocs-material. It is very memorable because I want it to be immediately available when you need it. All the documentation has been rewritten (except for a small part that is waiting to be updated) and is much better and easier to understand than the original.
5. Create a Discord community: I recently learned that most people prefer to use Discord, so I created a server: https://discord.gg/fPKVZScPT7
DebugInfo is still under active development, and I plan to focus on mining more symbols to improve decompilation quality.
If you have any questions, please raise an issue, thanks everyone!!