Timeline for Split binary data of fixed byte offset by byte position?
Current License: CC BY-SA 3.0
21 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 30, 2016 at 14:23 | vote | accept | Léo Léopold Hertz 준영 | ||
| Jun 30, 2015 at 9:35 | history | edited | Léo Léopold Hertz 준영 | CC BY-SA 3.0 |
clearer
|
| Jun 30, 2015 at 9:19 | history | edited | Léo Léopold Hertz 준영 | CC BY-SA 3.0 |
picture of the data format
|
| Jun 30, 2015 at 9:11 | history | edited | Léo Léopold Hertz 준영 | CC BY-SA 3.0 |
details
|
| Jun 30, 2015 at 9:03 | history | edited | Léo Léopold Hertz 준영 | CC BY-SA 3.0 |
names of files added for better readability
|
| Jun 27, 2015 at 20:11 | history | edited | Léo Léopold Hertz 준영 | CC BY-SA 3.0 |
regex not needed in grep, thank you Mikeserv!
|
| Jun 27, 2015 at 19:38 | history | edited | Léo Léopold Hertz 준영 | CC BY-SA 3.0 |
clearer
|
| Jun 27, 2015 at 18:59 | comment | added | mikeserv |
You should really drop that -P ON grep - it's not doing you any favors there. In general, just dump the file with od or strings or whatever and grep the results - you don't need to save a copy of the whole encoded file, though - you already have the other. And grepping stuff like that is already going to be tedious enough, and so maybe just keep that actual searches basic if you can.
|
|
| Jun 27, 2015 at 17:08 | answer | added | mikeserv | timeline score: 1 | |
| Jun 27, 2015 at 16:06 | answer | added | Léo Léopold Hertz 준영 | timeline score: 2 | |
| Jun 27, 2015 at 15:04 | history | edited | Léo Léopold Hertz 준영 | CC BY-SA 3.0 |
added binary example data
|
| Jun 27, 2015 at 11:44 | history | edited | Léo Léopold Hertz 준영 | CC BY-SA 3.0 |
outputs
|
| Jun 27, 2015 at 6:19 | answer | added | meuh | timeline score: 2 | |
| Jun 26, 2015 at 17:37 | comment | added | Léo Léopold Hertz 준영 | @godlygeek Sorry for my mistake. I added correct data now as a link. The byte distance is now 48300 (60*805). There are two headers in the data. I tried to simplify the original data unsuccessfully. | |
| Jun 26, 2015 at 17:36 | history | edited | Léo Léopold Hertz 준영 | CC BY-SA 3.0 |
correct data
|
| Jun 26, 2015 at 17:19 | history | edited | Léo Léopold Hertz 준영 | CC BY-SA 3.0 |
added 108 characters in body
|
| Jun 26, 2015 at 17:13 | comment | added | godlygeek |
Unless I'm missing something, that seems to be splitting in the middle of a byte - fafafafad0 starts at character 195 of the hex dump, meaning it's byte 98 of the binary file, but fafafafa6a starts at character 968 of the hex dump, 773 characters of hex later, which means it's 386.5 bytes later, which means it's across a byte boundary. Your "file 001.txt" is 773 characters long, which isn't normally a valid length for a hex dump - hex dumps must have an even number of characters, since each byte of the input is 2 characters.
|
|
| Jun 26, 2015 at 17:00 | comment | added | Léo Léopold Hertz 준영 | @godlygeek I added the wanted output in two files. | |
| Jun 26, 2015 at 16:59 | history | edited | Léo Léopold Hertz 준영 | CC BY-SA 3.0 |
wanted output added
|
| Jun 26, 2015 at 16:55 | comment | added | godlygeek |
Can you show exactly what you want the end result to be? I'm having trouble following your question. Most likely the most convenient tool for extracting a chunk of a binary file will be dd, but without understanding exactly what chunk you want to extract I'm limiting to making this a comment rather than an answer.
|
|
| Jun 26, 2015 at 15:22 | history | asked | Léo Léopold Hertz 준영 | CC BY-SA 3.0 |