NATIVE WINDOWS · DELPHI / C++BUILDER

Your binaries,
beyond the text dump.

Inspect packages, symbols, imports, and relocations in a native workspace—with the original TDUMP report within reach.

A Delphi package with its Borland symbol tree, selected S_GDATA32 record fields, and corresponding highlighted RAW source — Delphi package / A global symbol, its record fields, and the matching RAW report line.Inspect original ↗

Built with Delphi + VCLTDUMP / TDUMP64Open source · MITWindows x64

INSIDE A DELPHI PACKAGE

A symbol is more useful
when you can follow it.

From the symbol table to the record fields to the exact report text. The interpretation and its evidence belong together.

01
Find the record
Browse the Borland debug subsections, then select a global symbol.
sstGlobalSym → S_GDATA32
02
Read its structure
Inspect the record kind, name, segment, and address as individual fields.
03
Check the source
Enable Follow Selection to bring supported source ranges into view in the syntax-highlighted RAW panel.

See this record in the application ↗

SELECTED SYMBOLBorland debug information

@Sysinit@ModuleIsLib

Fields from the captured application view

Record kind: S_GDATA32
Record offset: 040D3
Type: bool8
Name index: 04D
Segment: 0004
Address: 00000

Corresponding RAW text● Source-backed

00000361: 040D3  S_GDATA32  type: bool8
          0004:00000  @Sysinit@ModuleIsLib [04D]
          Browser offset: 0000
00000362:     flags: 0000

Excerpt from the screenshot, wrapped for readability. This is an illustrated example, not a running browser version of TDump Explorer.

Actual symbol detail panel showing S_GDATA32 and @Sysinit@ModuleIsLib — THE ACTUAL INTERFACE Native record rendering. No reconstructed UI.

INSPECT YOUR BUILD ARTIFACTS

Different formats.
The same way in.

Start with the question you need to answer. Navigate the structures that TDUMP exposes.

PE / PORTABLE EXECUTABLE

What does this package import—and what does it expose?

Inspect Windows executables, DLLs, and Delphi packages through their headers, directories, and structured tables.

DOS & PE headers
Data directories
Sections
Imports & delayed imports
Exports
Resources
Base relocations

Coverage follows the selected TDUMP version. Unknown or unsupported content can remain available through diagnostics and source-backed fallback views.

FROM INSPECTION TO YOUR WORKFLOW

Keep the findings.
Lose the retyping.

Copy selected rows as text, CSV, JSON, or Markdown. Bring a structured result into a script, a spreadsheet, or an issue report.

EXAMPLE SELECTION · ELF SYMBOL TABLEFive globals from zutil.oFunctions and an object · .symtab
Values and sizes preserved in hexadecimal

[
  {"Name":"zError", "Value":"20", "Size":"29", "Type":"FUNC", "Binding":"GLOBAL"},
  {"Name":"z_errmsg", "Value":"0", "Size":"50", "Type":"OBJECT", "Binding":"GLOBAL"},
  {"Name":"zcalloc", "Value":"50", "Size":"11", "Type":"FUNC", "Binding":"GLOBAL"},
  {"Name":"zcfree", "Value":"70", "Size":"D", "Type":"FUNC", "Binding":"GLOBAL"},
  {"Name":"zlibCompileFlags", "Value":"10", "Size":"B", "Type":"FUNC", "Binding":"GLOBAL"}
]

Five rows from ELF.Object.Win64.tdump, used by the parser tests. View fixture text ↗

NATIVE BY DESIGN

Keep your inspections
in one workspace.

Open several binaries and reports in separate tabs. Each document keeps its structured data and original TDUMP report together.

TDump Explorer’s native document tabs: ELF, a Delphi package, and the active Mach-O report, with new-document and recent-file controls — DOCUMENT TABS Three open inspections · view the full workspace ↗

A native Windows workflow.

Drop files onto the window, reopen a recent report, or queue several inputs for analysis.

Per-monitor DPI awareness sizes controls for each display. Choose light, dark, or system themes.

TDump Explorer’s binary-file icon and Drag & drop a report or binary instruction in the dark-theme drop zone — DRAG & DROP View the full application window ↗

THE LARGE-REPORT PATH

Read what you need.
Render what you see.

Memory-mapped inputAccess the report without first duplicating it as one complete string.
Indexed lines & lazy decodingLocate source ranges and decode their text when requested.
Virtualized viewsKeep large tables and filtered RAW results navigable.

Documented regression fixture: 1,052,806 linesCurrent report-size limit: 100 MiBNot a debugger or disassembler.

START WITH WHAT YOU HAVE

Open a report.
Or start from the binary.

.tdump / compatible text

You already have the report.

Open it, drop it onto the application, or pass its path on the command line. Navigate the structured tree and keep RAW output beside it.

No TDUMP installation required.

.exe / .dll / .bpl / and more

You have a build artifact.

Open the supported binary. TDump Explorer locates TDUMP or TDUMP64, generates a report, and opens the result in a document tab.

Requires TDUMP from a Delphi / RAD Studio installation.

Recognized inputs and coverage notes

Recognized file extensions and inspection coverage
Input family	Recognized files	Coverage notes
Windows binaries	`.exe` `.dll` `.bpl` `.dpl` `.ocx` `.cpl` `.scr` `.com` `.sys`	PE headers, sections, imports, exports, resources, and relocations where emitted by TDUMP.
Objects & libraries	`.obj` `.o` `.lib` `.ar` `.a`	Object records and archive members. COFF input may use diagnostic or fallback views.
ELF	`.elf` `.so`	Headers, sections, program headers, symbols, dynamic entries, and relocations.
Mach-O	`.dylib` `.bundle` `.mach`	Architectures, load commands, sections, symbols, imports, and binding information.
Delphi units	`.dcu`	Diagnostic or fallback views when TDUMP cannot emit a normal structured report.
Existing reports	`.tdump` and compatible text reports	Open directly. No TDUMP installation required.

Binary inputs require TDUMP or TDUMP64. Extension recognition does not guarantee full coverage; results depend on the report emitted by the installed tool. Some format-specific payloads remain generic or source-backed.

Source available under the MIT license. Packaged builds, when published, are listed on Releases.

View on GitHub ↗Releases ↗

Your binaries,beyond the text dump.

A symbol is more usefulwhen you can follow it.

Find the record

Read its structure

Check the source