---
name: "coreinject"
section: "1"
platform: "linux"
package: "minicoredumper-utils"
version: "2.0.7-4"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/coreinject"
---

# coreinject(1)

inject binary dumps from minicoredumper(1) into a core file

## NAME

coreinject - inject binary dumps from [**minicoredumper**(1)](/minicoredumper/1.md) into a core file

## SYNOPSIS

**coreinject** \[*OPTION*\]... *core* *symbol.map* *binary-dump*...

## DESCRIPTION

If an application using [**libminicoredumper**(7)](/libminicoredumper/7.md) registers a binary dump to not be included in the core file, the [**minicoredumper**(1)](/minicoredumper/1.md) will create a separate dump file containing the contents of that variable. A symbol map file *symbol.map* is also created by the [**minicoredumper**(1)](/minicoredumper/1.md)**.** Using these files, **coreinject** can inject that binary data into the stripped *core* file for use with [**gdb**(1)](/gdb/1.md).

The options are as follows:

- **--data=***IDENT*:*SIZE*@*SRCFILE*+*SRCOFF*

  Inject *SIZE* bytes of data at offset *SRCOFF* of file *SRCFILE* to the [**core**(5)](/core/5.md). The data is injected at the location of the *IDENT* as stored in the symbol map. This option is useful for injecting data other than that which was actually dumped by the [**minicoredumper**(1)](/minicoredumper/1.md).

## NOTES

If the binary dump used *MCD\_DATA\_PTR\_DIRECT*, the separate binary file contains exactly that data. If *MCD\_DATA\_PTR\_INDIRECT* was used, the separate binary file contains first the pointer value followed by the data pointed to by the pointer.

## EXAMPLE

Insert the binary data in *bdump.bin* into *core*.

coreinject core symbol.map bdump.bin

## SEE ALSO

[**minicoredumper**(1)](/minicoredumper/1.md), [**libminicoredumper**(7)](/libminicoredumper/7.md), [**mcd\_dump\_data\_register\_bin**(3)](/mcd_dump_data_register_bin/3.md)

The DiaMon Workgroup: \<http://www.diamon.org\>