Welcome to ghidra Discussions!

[emteere]

Welcome!

With the new year fast approaching and a preview feature on the way, now seemed like a good time to open github Discussions.

We’re hoping to use Discussions as a place to better manage our connection with the community. We hope you will:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and be open-minded.

Please bear with us as the team gets used to this new discussion area. The organization will likely evolve over time. If there are bugs or issues you are encountering please post them in the Issues section. For questions and general discussions about ghidra features please open a discussion here. We'll monitor and respond as best we can.

[MaheraMihanta]

bonjour tout le monde, je suis sur une décompilation avec ghidra, je ne connais pas vraiment l'assembleur, par contre je peux tout à fait me débrouiller en python, ou autre language, ma question: comment transcrire le résultat de la décompilation issu de ghidra en Python? à la limite en C ou C++ ou Java

[d-millar]

Les résultats de la décompilation devraient être proches du C compilable. Rendre les résultats dans quelque chose de plus proche de Python serait tout un projet et n'est pas actuellement sur notre radar. (Toutes mes excuses par avance pour l'utilisation de Google Translate.)

[MaheraMihanta]

Thank you for paying attention to the comment I left. Currently, I am working on decompiling some software from the company where I work. These are really old software, written in 16 bits. The goal is to recreate the scenarios, rebuild the graphical interfaces, and all the functionalities with them. I specialize in Python; however, I am also quite knowledgeable in C and C++. Once we have succeeded in translating the resulting C code from Ghidra, we will share the results of the research with you if you want Le sam. 6 avr. 2024 à 18:59, d-millar ***@***.***> a écrit :

…

Les résultats de la décompilation devraient être proches du C compilable. Rendre les résultats dans quelque chose de plus proche de Python serait tout un projet et n'est pas actuellement sur notre radar. (Toutes mes excuses par avance pour l'utilisation de Google Translate.) — Reply to this email directly, view it on GitHub <#2563 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BHTZEJ3ARWPZWKKEWWFUBIDY4AZZJAVCNFSM4U6P57TKU5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TSMBTGA4TQOA> . You are receiving this because you commented.Message ID: <NationalSecurityAgency/ghidra/repo-discussions/2563/comments/9030988@ github.com>

[stephen-hocking]

I'm trying to convert the asm portions of https://github.com/dkfans/keeperfx/blob/master/src/bflib_render_gpoly.c back into C. Have succeeded to a certain point, but I've been hand converting the _DAT_00blah variable references in the decompiled code back into the actual variable names by hand, which is tedious & error prone. Is there an automated way to do this? The .o file is compiled with gcc's -g option, which should put all the debug symbols in.