Get Thomas Cook App for
deals on flights, Stay & activities
Download the App Now
We use cookies to improve your website experience and provide more personalized services to you, both on this website and through other media. By continuing to use this website, you agree to our use of cookies as explained in our Cookie Policy. Please read our Cookie Policy for more information on how we use cookies and how you can disable them.
I understandReverse engineering legacy software requires specialized tools capable of translating compiled machine code back into human-readable structures. For applications built using Borland Delphi, one tool stands out historically as a foundational asset for analysts: .
current_component = None indent_stack = [] delphi decompiler dede
What is your ? (e.g., recovering lost source code, finding a bug, analyzing a file?) Are you working with a 32-bit or 64-bit executable?
# Detect event handlers if prop_name.lower().endswith('on'): # Event handler reference event_handler = EventHandler( event_name=prop_name, method_name=prop_value, rva=0 # Would need actual RVA calculation ) component.events.append(event_handler) else: # Regular property prop_type = self._guess_property_type(prop_value) rtti_prop = RTTIProperty( name=prop_name, value=prop_value, prop_type=prop_type ) component.properties[prop_name] = rtti_prop
💡 : Use DeDe alongside a debugger like x64dbg or OllyDbg to step through the code once DeDe gives you the correct entry points. If you'd like, I can: Help you install and set up DeDe Explain how to handle obfuscated files
If you want, I can:
Because DeDe is a well‑known tool, many Delphi protectors and packers include specific anti‑DeDe defenses. These can check for DeDe’s window class name (“DeDe”) or modify the binary in ways that confuse DeDe’s parser. The variant tries to circumvent such checks by renaming internal identifiers, but aggressive commercial protectors (like Armadillo, ASProtect, or Enigma Protector) will still render DeDe ineffective.
def find_event_handlers(self) -> Dict[str, List[int]]: """Find event handler addresses in code section""" handlers = {} These can check for DeDe’s window class name
str_len = self.file_data[offset] if 1 <= str_len <= 100: # Reasonable string length try: name = self.file_data[offset+1:offset+1+str_len].decode('ascii', errors='ignore') if name and name[0].isalpha(): return name except: pass return None
Fill in the email Address that you used to register or book with Thomascook.
We will reset and send your new password.
Please enter the valid email address
Your request for new password has been accepted.
The new password would be emailed to the registered email address, if not registered please do the same but aggressive commercial protectors (like Armadillo
Reverse engineering legacy software requires specialized tools capable of translating compiled machine code back into human-readable structures. For applications built using Borland Delphi, one tool stands out historically as a foundational asset for analysts: .
current_component = None indent_stack = []
What is your ? (e.g., recovering lost source code, finding a bug, analyzing a file?) Are you working with a 32-bit or 64-bit executable?
# Detect event handlers if prop_name.lower().endswith('on'): # Event handler reference event_handler = EventHandler( event_name=prop_name, method_name=prop_value, rva=0 # Would need actual RVA calculation ) component.events.append(event_handler) else: # Regular property prop_type = self._guess_property_type(prop_value) rtti_prop = RTTIProperty( name=prop_name, value=prop_value, prop_type=prop_type ) component.properties[prop_name] = rtti_prop
💡 : Use DeDe alongside a debugger like x64dbg or OllyDbg to step through the code once DeDe gives you the correct entry points. If you'd like, I can: Help you install and set up DeDe Explain how to handle obfuscated files
If you want, I can:
Because DeDe is a well‑known tool, many Delphi protectors and packers include specific anti‑DeDe defenses. These can check for DeDe’s window class name (“DeDe”) or modify the binary in ways that confuse DeDe’s parser. The variant tries to circumvent such checks by renaming internal identifiers, but aggressive commercial protectors (like Armadillo, ASProtect, or Enigma Protector) will still render DeDe ineffective.
def find_event_handlers(self) -> Dict[str, List[int]]: """Find event handler addresses in code section""" handlers = {}
str_len = self.file_data[offset] if 1 <= str_len <= 100: # Reasonable string length try: name = self.file_data[offset+1:offset+1+str_len].decode('ascii', errors='ignore') if name and name[0].isalpha(): return name except: pass return None