Skip to main content
Information Security

Return to Answer

deleted 92 characters in body
Source Link
schroeder ♦
schroeder ♦
  • 132.1k
  • 55
  • 307
  • 348

I know this question is already a bit older but:

Just in case someone else runs into this problem. If you want to enter high bytes into stdin (for example when debugging with gdb in a shell) then you first have to change the encoding of the terminal emulator you are using from UTF-8 to ISO-8859-1 or smth.something similar so your entered bytes don't get converted into smth.something else.

Once you have done this you can enter the byte values with ctrl+shift+uctrl+shift+u and the hex number.

I know this question is already a bit older but:

Just in case someone else runs into this problem. If you want to enter high bytes into stdin (for example when debugging with gdb in a shell) then you first have to change the encoding of the terminal emulator you are using from UTF-8 to ISO-8859-1 or smth. similar so your entered bytes don't get converted into smth. else.

Once you have done this you can enter the byte values with ctrl+shift+u and the hex number.

If you want to enter high bytes into stdin (for example when debugging with gdb in a shell) then you first have to change the encoding of the terminal emulator you are using from UTF-8 to ISO-8859-1 or something similar so your entered bytes don't get converted into something else.

Once you have done this you can enter the byte values with ctrl+shift+u and the hex number.

Source Link
Arwez
Arwez
  • 1

I know this question is already a bit older but:

Just in case someone else runs into this problem. If you want to enter high bytes into stdin (for example when debugging with gdb in a shell) then you first have to change the encoding of the terminal emulator you are using from UTF-8 to ISO-8859-1 or smth. similar so your entered bytes don't get converted into smth. else.

Once you have done this you can enter the byte values with ctrl+shift+u and the hex number.