strToHex ( string to its hex representation as string)Integer-to-hex string generatorConvert hex string to byte arrayString representation of TreeSimple string inverter programSimple string repeater programSorting a String based on its wordsGeneric Pairing Heap PerformanceHex-string representation of a byte arrayConvert hex color string to SDL ColorConvert string of hex into vector of bytes

I’m planning on buying a laser printer but concerned about the life cycle of toner in the machine

How to use Pandas to get the count of every combination inclusive

Is Social Media Science Fiction?

Is it legal to have the "// (c) 2019 John Smith" header in all files when there are hundreds of contributors?

If Manufacturer spice model and Datasheet give different values which should I use?

Why is this code 6.5x slower with optimizations enabled?

Is it possible to make sharp wind that can cut stuff from afar?

A newer friend of my brother's gave him a load of baseball cards that are supposedly extremely valuable. Is this a scam?

Schwarzchild Radius of the Universe

Motorized valve interfering with button?

A Journey Through Space and Time

Could a US political party gain complete control over the government by removing checks & balances?

Calculus Optimization - Point on graph closest to given point

What is the offset in a seaplane's hull?

How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?

Infinite past with a beginning?

What Brexit solution does the DUP want?

How is it possible for user's password to be changed after storage was encrypted? (on OS X, Android)

Prevent a directory in /tmp from being deleted

How do you conduct xenoanthropology after first contact?

Should I join an office cleaning event for free?

Example of a relative pronoun

Copycat chess is back

Accidentally leaked the solution to an assignment, what to do now? (I'm the prof)



strToHex ( string to its hex representation as string)


Integer-to-hex string generatorConvert hex string to byte arrayString representation of TreeSimple string inverter programSimple string repeater programSorting a String based on its wordsGeneric Pairing Heap PerformanceHex-string representation of a byte arrayConvert hex color string to SDL ColorConvert string of hex into vector of bytes






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








8












$begingroup$


I want to convert strings to their hex representations as strings too (like hex dump programs), for example "abz" to "61627A".



char * strToHex( char * str )

int length = strlen ( str );
char * newStr = malloc( length * 2 );
if ( !newStr ) shutDown ( "can't alloc memory" ) ;

for ( int x = 0; x < length; x++)
char y = str[ x ];
sprintf ( newStr + x * 2, "%02X", y );

return newStr;



ShutDown definition is omitted here, it is a function that calls perror and exit()



I designed strToHex to be used like



char * str = "abcdefghijklmnopqrstuvwxyz";
char * hex = strToHex(str);
printf("%sn",hex);
//outputs : 6162636465666768696A6B6C6D6E6F707172737475767778797A









share|improve this question











$endgroup$







  • 3




    $begingroup$
    I'd be really interested to see what shutdown(char* msg) does.
    $endgroup$
    – pacmaninbw
    yesterday










  • $begingroup$
    In the use case that was provided, since you can effectively predict the size, I would think it would be more natural to have a string buffer and the size passed in instead of creating it dynamically.
    $endgroup$
    – Neil Edelman
    yesterday






  • 1




    $begingroup$
    Won't printf() require hex to have a trailing byte?
    $endgroup$
    – jochen
    21 hours ago










  • $begingroup$
    @pacmaninbw The argument name is actually "msg" as you guessed 😂 . void shutDown(char * msg) perror(msg); exit(EXIT_FAILURE);
    $endgroup$
    – Accountant م
    14 hours ago










  • $begingroup$
    @jochen Yes, thank you, I forgot to terminate newStr, and I was unlucky the couple of tests that I run didn't fail.
    $endgroup$
    – Accountant م
    14 hours ago

















8












$begingroup$


I want to convert strings to their hex representations as strings too (like hex dump programs), for example "abz" to "61627A".



char * strToHex( char * str )

int length = strlen ( str );
char * newStr = malloc( length * 2 );
if ( !newStr ) shutDown ( "can't alloc memory" ) ;

for ( int x = 0; x < length; x++)
char y = str[ x ];
sprintf ( newStr + x * 2, "%02X", y );

return newStr;



ShutDown definition is omitted here, it is a function that calls perror and exit()



I designed strToHex to be used like



char * str = "abcdefghijklmnopqrstuvwxyz";
char * hex = strToHex(str);
printf("%sn",hex);
//outputs : 6162636465666768696A6B6C6D6E6F707172737475767778797A









share|improve this question











$endgroup$







  • 3




    $begingroup$
    I'd be really interested to see what shutdown(char* msg) does.
    $endgroup$
    – pacmaninbw
    yesterday










  • $begingroup$
    In the use case that was provided, since you can effectively predict the size, I would think it would be more natural to have a string buffer and the size passed in instead of creating it dynamically.
    $endgroup$
    – Neil Edelman
    yesterday






  • 1




    $begingroup$
    Won't printf() require hex to have a trailing byte?
    $endgroup$
    – jochen
    21 hours ago










  • $begingroup$
    @pacmaninbw The argument name is actually "msg" as you guessed 😂 . void shutDown(char * msg) perror(msg); exit(EXIT_FAILURE);
    $endgroup$
    – Accountant م
    14 hours ago










  • $begingroup$
    @jochen Yes, thank you, I forgot to terminate newStr, and I was unlucky the couple of tests that I run didn't fail.
    $endgroup$
    – Accountant م
    14 hours ago













8












8








8





$begingroup$


I want to convert strings to their hex representations as strings too (like hex dump programs), for example "abz" to "61627A".



char * strToHex( char * str )

int length = strlen ( str );
char * newStr = malloc( length * 2 );
if ( !newStr ) shutDown ( "can't alloc memory" ) ;

for ( int x = 0; x < length; x++)
char y = str[ x ];
sprintf ( newStr + x * 2, "%02X", y );

return newStr;



ShutDown definition is omitted here, it is a function that calls perror and exit()



I designed strToHex to be used like



char * str = "abcdefghijklmnopqrstuvwxyz";
char * hex = strToHex(str);
printf("%sn",hex);
//outputs : 6162636465666768696A6B6C6D6E6F707172737475767778797A









share|improve this question











$endgroup$




I want to convert strings to their hex representations as strings too (like hex dump programs), for example "abz" to "61627A".



char * strToHex( char * str )

int length = strlen ( str );
char * newStr = malloc( length * 2 );
if ( !newStr ) shutDown ( "can't alloc memory" ) ;

for ( int x = 0; x < length; x++)
char y = str[ x ];
sprintf ( newStr + x * 2, "%02X", y );

return newStr;



ShutDown definition is omitted here, it is a function that calls perror and exit()



I designed strToHex to be used like



char * str = "abcdefghijklmnopqrstuvwxyz";
char * hex = strToHex(str);
printf("%sn",hex);
//outputs : 6162636465666768696A6B6C6D6E6F707172737475767778797A






beginner c strings






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited yesterday









mdfst13

17.9k62257




17.9k62257










asked yesterday









Accountant مAccountant م

22418




22418







  • 3




    $begingroup$
    I'd be really interested to see what shutdown(char* msg) does.
    $endgroup$
    – pacmaninbw
    yesterday










  • $begingroup$
    In the use case that was provided, since you can effectively predict the size, I would think it would be more natural to have a string buffer and the size passed in instead of creating it dynamically.
    $endgroup$
    – Neil Edelman
    yesterday






  • 1




    $begingroup$
    Won't printf() require hex to have a trailing byte?
    $endgroup$
    – jochen
    21 hours ago










  • $begingroup$
    @pacmaninbw The argument name is actually "msg" as you guessed 😂 . void shutDown(char * msg) perror(msg); exit(EXIT_FAILURE);
    $endgroup$
    – Accountant م
    14 hours ago










  • $begingroup$
    @jochen Yes, thank you, I forgot to terminate newStr, and I was unlucky the couple of tests that I run didn't fail.
    $endgroup$
    – Accountant م
    14 hours ago












  • 3




    $begingroup$
    I'd be really interested to see what shutdown(char* msg) does.
    $endgroup$
    – pacmaninbw
    yesterday










  • $begingroup$
    In the use case that was provided, since you can effectively predict the size, I would think it would be more natural to have a string buffer and the size passed in instead of creating it dynamically.
    $endgroup$
    – Neil Edelman
    yesterday






  • 1




    $begingroup$
    Won't printf() require hex to have a trailing byte?
    $endgroup$
    – jochen
    21 hours ago










  • $begingroup$
    @pacmaninbw The argument name is actually "msg" as you guessed 😂 . void shutDown(char * msg) perror(msg); exit(EXIT_FAILURE);
    $endgroup$
    – Accountant م
    14 hours ago










  • $begingroup$
    @jochen Yes, thank you, I forgot to terminate newStr, and I was unlucky the couple of tests that I run didn't fail.
    $endgroup$
    – Accountant م
    14 hours ago







3




3




$begingroup$
I'd be really interested to see what shutdown(char* msg) does.
$endgroup$
– pacmaninbw
yesterday




$begingroup$
I'd be really interested to see what shutdown(char* msg) does.
$endgroup$
– pacmaninbw
yesterday












$begingroup$
In the use case that was provided, since you can effectively predict the size, I would think it would be more natural to have a string buffer and the size passed in instead of creating it dynamically.
$endgroup$
– Neil Edelman
yesterday




$begingroup$
In the use case that was provided, since you can effectively predict the size, I would think it would be more natural to have a string buffer and the size passed in instead of creating it dynamically.
$endgroup$
– Neil Edelman
yesterday




1




1




$begingroup$
Won't printf() require hex to have a trailing byte?
$endgroup$
– jochen
21 hours ago




$begingroup$
Won't printf() require hex to have a trailing byte?
$endgroup$
– jochen
21 hours ago












$begingroup$
@pacmaninbw The argument name is actually "msg" as you guessed 😂 . void shutDown(char * msg) perror(msg); exit(EXIT_FAILURE);
$endgroup$
– Accountant م
14 hours ago




$begingroup$
@pacmaninbw The argument name is actually "msg" as you guessed 😂 . void shutDown(char * msg) perror(msg); exit(EXIT_FAILURE);
$endgroup$
– Accountant م
14 hours ago












$begingroup$
@jochen Yes, thank you, I forgot to terminate newStr, and I was unlucky the couple of tests that I run didn't fail.
$endgroup$
– Accountant م
14 hours ago




$begingroup$
@jochen Yes, thank you, I forgot to terminate newStr, and I was unlucky the couple of tests that I run didn't fail.
$endgroup$
– Accountant م
14 hours ago










4 Answers
4






active

oldest

votes


















8












$begingroup$

Bug



As Carsten points out, you need to allocate $(textlengthcdot 2)+1$ bytes, rather than $(textlengthcdot2)$ to account for the null terminator sprintf() adds.



Formatting



Most C formatting guides do not include spaces around the arguments to function calls, nor the expressions within an if-statement. For an example of a C style most C programmers would find acceptable, see OpenBSD's style(9) manual.



I choose to associate * with the variable name, rather than floating between the type and name. This disambiguates the following example:



int *a, b;


Here, a is a pointer to an integer, but b is only an integer. By moving the asterisk next to the name, it makes this clearer.



int length = strlen ( str );
char * newStr = malloc (length * 2 );
if ( !newStr) shutDown ( "can't allocate memory" ) ;


Becomes:



int const len = strlen(str);
char *const new_str = malloc(1 + len * 2);

if (new_str == NULL)
shutDown("can't allocate memory");



Error checking



Rather than calling shutDown() and exit()ing the program, you should instead return an error value which can be checked by the caller of str_to_hex(). Because you return a pointer, you can return NULL to indicate an error occurred and the caller should check errno.



Likewise, on some systems your program can incorrectly exit when length == 0. If we look at the manual page for malloc(3):




Return Value



The malloc() and calloc() functions return a pointer to the allocated memory that is suitably aligned for any kind of variable. On error, these functions return NULL. NULL may also be returned by a successful call to malloc() with a size of zero, or by a successful call to calloc() with nmemb or size equal to zero.




So by returning NULL we account for the case where malloc(3) returns NULL on success.



if (new_str == NULL) 
shutDown("can't alloc memory");



Becomes:



if (new_str == NULL) 
return NULL;



If you choose, you can also check if str is NULL before calling strlen(). This is up to you, and it's not uncommon in C to ignore this case and leave it as user error.



Looping



Use the size_t type in your loop rather than int. size_t is guaranteed be wide enough to hold any array index, while int is not.



Using i rather than x is more common for looping variables.



The y variable isn't needed. You can simply use str[i] in its place.



In terms of performance there's likely a faster option than using sprintf(). You should look into strtol(3).



Conclusion



Here is the code I ended up with:



#include <stdio.h>
#include <stdlib.h>
#include <string.h>

char *
str_to_hex(char const *const str)

size_t const len = strlen(str);

char *const new_str = malloc(1 + len * 2);

if (new_str == NULL)
return NULL;


for (size_t i = 0; i < len; ++i)
sprintf(new_str + i * 2, "%02X", str[i]);


return new_str;


int
main(void)

char *str = "abz";
char *hex = str_to_hex(str);

if (hex == NULL && strlen(str) != 0)
/* error ... */


printf("%sn",hex);

free(hex);



Hope this helps!






share|improve this answer











$endgroup$








  • 1




    $begingroup$
    Won't printf() require hex to have a trailing byte?
    $endgroup$
    – jochen
    21 hours ago






  • 3




    $begingroup$
    You should allocate 2*len+1 bytes.
    $endgroup$
    – Carsten S
    20 hours ago










  • $begingroup$
    Good advice but it fails to fix the bug in OP’s code.
    $endgroup$
    – Konrad Rudolph
    15 hours ago










  • $begingroup$
    sprintf adds a null terminator. @Carsten thanks, I forgot to include that, I'll update my answer
    $endgroup$
    – esote
    15 hours ago






  • 1




    $begingroup$
    @Accountantم It is from the OpenBSD manual, the style is called BSD kernel normal form (KNF). Around the middle of manual: "The function type should be on a line by itself preceding the function."
    $endgroup$
    – esote
    12 hours ago



















2












$begingroup$

In my opinion, the most severe problem is "Insufficient target memory".



int length = strlen ( str );
char * newStr = malloc( length * 2 );


You are allocating twice the length of str, which is enough for all the hex characters (two hex chars per input byte).



But sprintf works different: "A terminating null character is automatically appended after the content" (see here).



So the last call to sprintf will write a terminating zero byte right after newStr, into unallocated memory. This might provoke all kinds of unintended behaviour, including (but not limited to) crashes.






share|improve this answer









$endgroup$












  • $begingroup$
    Yes thank you, it's a bug. I forgot to terminate newStr, thanks for highlighting this as it's the biggest problem in my code.
    $endgroup$
    – Accountant م
    14 hours ago


















1












$begingroup$

Just one addition: like asprintf vs snprintf. One can effectively predict the size, so I would think it natural to have a string buffer and the size passed in instead of creating it dynamically.



#include <stdlib.h> /* strtol */
#include <string.h> /* strlen */
#include <stdio.h> /* printf */
#include <assert.h> /* assert */

/** Converts str to the underlying bit representation in hex, stored in
hex. It may fail to compute the entire string due to hex_size, in which
case the return will be less then the str length.
str: A valid null-terminated string.
hex: The output string.
hex_size: The output string's size.
return: The number of characters from the original that it processed. */
static size_t strToHex(const char *str, char *hex, size_t hex_size)

static const char digits[0x0F] = '0', '1', '2', '3', '4', '5',
'6', '7', '8', '9', 'A', 'B', 'C', 'E', 'F' ;
const size_t str_len = strlen(str), hex_len = hex_size - 1;
const size_t length = str_len < hex_len / 2 ? str_len : hex_len / 2;
const char *s = str;
char *h = hex;
size_t x;
assert(str && hex);
if(!hex_size) return 0;
for(x = 0; x < length; x++)
*h++ = digits[(*s & 0xF0) >> 4], *h++ = digits[*s++ & 0x0F];
*h = '';
return s - str;


int main(void)

const char *str = "abcdefghijklmnopqrstuvwxyz", *str2 = "æôƌԹظⓐa";
char hex[80];
size_t ret;
ret = strToHex(str, hex, sizeof hex);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str, hex, sizeof hex / 2);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str, hex, 0);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str2, hex, sizeof hex);
printf(""%s" -> "%s" (%lu.)n", str2, hex, (unsigned long)ret);
return EXIT_SUCCESS;



It cannot really fail if given the proper input, so this simplifies error checking a lot, especially in C. malloc and sprintf are pretty slow functions, comparatively, so I expect this to be faster and more robust.






share|improve this answer











$endgroup$












  • $begingroup$
    Thank you very much, I like the way you documented the function, is this a known convention for documenting C code ? I also like the performance consideration that this function has over the function I posted, but I generally give easier user interfaces more priority over performance, unless I get bottlenecks. I will study your code today again with a deeper look.
    $endgroup$
    – Accountant م
    14 hours ago


















0












$begingroup$

I did more tests on the function today and found another Bug (shame on me), and AFAIK on code review I can't change the original code in the question since it got reviews.



if there are bytes have values more than 127 it will be all displayed as FF by the function. To reproduce



char str[] = 127,0;
char * hex = strToHex(str);
printf("%sn",hex); //pritnts 7F (NORMAL)

//now try with this
char str[] = 128,0;
char * hex = strToHex(str);
printf("%sn",hex); //pritnts FF (BUG)


It appears if the function is used with non English characters because they are stored with the most significant bit is set 1 in UTF-8



The Fix



To Fix it, replace this line



sprintf ( newStr + x * 2, "%02X", y );


with this



sprintf ( newStr + x * 2, "%02hhX", y ); // added hh


This is because y is of type char or signed char and the X specifier expects the argument to be unsigned int if no length is provided, so we provided length hh to tell the function that X is unsigned char . Check the length table of printf.



If we didn't provided hh, the sprintf function is going to promote Y from signed char to unsigned int and this promotion will go like this



when we defined the str as char and assigned the value 128 to it, it's represented as



1000 0000


The compiler thought it is -128 because it's type is signed char, now function sprintf wants to promote it to unsigned int, so to represent -128 in size of int, it will be like



1111 1111 1111 1111 1111 1111 1000 0000
^^^^ ^^^^ ^^^^ ^^^^


and because we chose to show only 2 digits then we see the last 2 bytes FF.



more info are here , and here






share|improve this answer









$endgroup$








  • 1




    $begingroup$
    This is only an issue on implementations that treat char as signed. If a char is unsigned it isn't a problem. Other possible fixes include declaring y as an unsigned char, casting y to an unsigned char in the sprintf call, or masking it (y & 0xFF).
    $endgroup$
    – 1201ProgramAlarm
    4 hours ago











Your Answer





StackExchange.ifUsing("editor", function ()
return StackExchange.using("mathjaxEditing", function ()
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix)
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
);
);
, "mathjax-editing");

StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "196"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f216992%2fstrtohex-string-to-its-hex-representation-as-string%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























4 Answers
4






active

oldest

votes








4 Answers
4






active

oldest

votes









active

oldest

votes






active

oldest

votes









8












$begingroup$

Bug



As Carsten points out, you need to allocate $(textlengthcdot 2)+1$ bytes, rather than $(textlengthcdot2)$ to account for the null terminator sprintf() adds.



Formatting



Most C formatting guides do not include spaces around the arguments to function calls, nor the expressions within an if-statement. For an example of a C style most C programmers would find acceptable, see OpenBSD's style(9) manual.



I choose to associate * with the variable name, rather than floating between the type and name. This disambiguates the following example:



int *a, b;


Here, a is a pointer to an integer, but b is only an integer. By moving the asterisk next to the name, it makes this clearer.



int length = strlen ( str );
char * newStr = malloc (length * 2 );
if ( !newStr) shutDown ( "can't allocate memory" ) ;


Becomes:



int const len = strlen(str);
char *const new_str = malloc(1 + len * 2);

if (new_str == NULL)
shutDown("can't allocate memory");



Error checking



Rather than calling shutDown() and exit()ing the program, you should instead return an error value which can be checked by the caller of str_to_hex(). Because you return a pointer, you can return NULL to indicate an error occurred and the caller should check errno.



Likewise, on some systems your program can incorrectly exit when length == 0. If we look at the manual page for malloc(3):




Return Value



The malloc() and calloc() functions return a pointer to the allocated memory that is suitably aligned for any kind of variable. On error, these functions return NULL. NULL may also be returned by a successful call to malloc() with a size of zero, or by a successful call to calloc() with nmemb or size equal to zero.




So by returning NULL we account for the case where malloc(3) returns NULL on success.



if (new_str == NULL) 
shutDown("can't alloc memory");



Becomes:



if (new_str == NULL) 
return NULL;



If you choose, you can also check if str is NULL before calling strlen(). This is up to you, and it's not uncommon in C to ignore this case and leave it as user error.



Looping



Use the size_t type in your loop rather than int. size_t is guaranteed be wide enough to hold any array index, while int is not.



Using i rather than x is more common for looping variables.



The y variable isn't needed. You can simply use str[i] in its place.



In terms of performance there's likely a faster option than using sprintf(). You should look into strtol(3).



Conclusion



Here is the code I ended up with:



#include <stdio.h>
#include <stdlib.h>
#include <string.h>

char *
str_to_hex(char const *const str)

size_t const len = strlen(str);

char *const new_str = malloc(1 + len * 2);

if (new_str == NULL)
return NULL;


for (size_t i = 0; i < len; ++i)
sprintf(new_str + i * 2, "%02X", str[i]);


return new_str;


int
main(void)

char *str = "abz";
char *hex = str_to_hex(str);

if (hex == NULL && strlen(str) != 0)
/* error ... */


printf("%sn",hex);

free(hex);



Hope this helps!






share|improve this answer











$endgroup$








  • 1




    $begingroup$
    Won't printf() require hex to have a trailing byte?
    $endgroup$
    – jochen
    21 hours ago






  • 3




    $begingroup$
    You should allocate 2*len+1 bytes.
    $endgroup$
    – Carsten S
    20 hours ago










  • $begingroup$
    Good advice but it fails to fix the bug in OP’s code.
    $endgroup$
    – Konrad Rudolph
    15 hours ago










  • $begingroup$
    sprintf adds a null terminator. @Carsten thanks, I forgot to include that, I'll update my answer
    $endgroup$
    – esote
    15 hours ago






  • 1




    $begingroup$
    @Accountantم It is from the OpenBSD manual, the style is called BSD kernel normal form (KNF). Around the middle of manual: "The function type should be on a line by itself preceding the function."
    $endgroup$
    – esote
    12 hours ago
















8












$begingroup$

Bug



As Carsten points out, you need to allocate $(textlengthcdot 2)+1$ bytes, rather than $(textlengthcdot2)$ to account for the null terminator sprintf() adds.



Formatting



Most C formatting guides do not include spaces around the arguments to function calls, nor the expressions within an if-statement. For an example of a C style most C programmers would find acceptable, see OpenBSD's style(9) manual.



I choose to associate * with the variable name, rather than floating between the type and name. This disambiguates the following example:



int *a, b;


Here, a is a pointer to an integer, but b is only an integer. By moving the asterisk next to the name, it makes this clearer.



int length = strlen ( str );
char * newStr = malloc (length * 2 );
if ( !newStr) shutDown ( "can't allocate memory" ) ;


Becomes:



int const len = strlen(str);
char *const new_str = malloc(1 + len * 2);

if (new_str == NULL)
shutDown("can't allocate memory");



Error checking



Rather than calling shutDown() and exit()ing the program, you should instead return an error value which can be checked by the caller of str_to_hex(). Because you return a pointer, you can return NULL to indicate an error occurred and the caller should check errno.



Likewise, on some systems your program can incorrectly exit when length == 0. If we look at the manual page for malloc(3):




Return Value



The malloc() and calloc() functions return a pointer to the allocated memory that is suitably aligned for any kind of variable. On error, these functions return NULL. NULL may also be returned by a successful call to malloc() with a size of zero, or by a successful call to calloc() with nmemb or size equal to zero.




So by returning NULL we account for the case where malloc(3) returns NULL on success.



if (new_str == NULL) 
shutDown("can't alloc memory");



Becomes:



if (new_str == NULL) 
return NULL;



If you choose, you can also check if str is NULL before calling strlen(). This is up to you, and it's not uncommon in C to ignore this case and leave it as user error.



Looping



Use the size_t type in your loop rather than int. size_t is guaranteed be wide enough to hold any array index, while int is not.



Using i rather than x is more common for looping variables.



The y variable isn't needed. You can simply use str[i] in its place.



In terms of performance there's likely a faster option than using sprintf(). You should look into strtol(3).



Conclusion



Here is the code I ended up with:



#include <stdio.h>
#include <stdlib.h>
#include <string.h>

char *
str_to_hex(char const *const str)

size_t const len = strlen(str);

char *const new_str = malloc(1 + len * 2);

if (new_str == NULL)
return NULL;


for (size_t i = 0; i < len; ++i)
sprintf(new_str + i * 2, "%02X", str[i]);


return new_str;


int
main(void)

char *str = "abz";
char *hex = str_to_hex(str);

if (hex == NULL && strlen(str) != 0)
/* error ... */


printf("%sn",hex);

free(hex);



Hope this helps!






share|improve this answer











$endgroup$








  • 1




    $begingroup$
    Won't printf() require hex to have a trailing byte?
    $endgroup$
    – jochen
    21 hours ago






  • 3




    $begingroup$
    You should allocate 2*len+1 bytes.
    $endgroup$
    – Carsten S
    20 hours ago










  • $begingroup$
    Good advice but it fails to fix the bug in OP’s code.
    $endgroup$
    – Konrad Rudolph
    15 hours ago










  • $begingroup$
    sprintf adds a null terminator. @Carsten thanks, I forgot to include that, I'll update my answer
    $endgroup$
    – esote
    15 hours ago






  • 1




    $begingroup$
    @Accountantم It is from the OpenBSD manual, the style is called BSD kernel normal form (KNF). Around the middle of manual: "The function type should be on a line by itself preceding the function."
    $endgroup$
    – esote
    12 hours ago














8












8








8





$begingroup$

Bug



As Carsten points out, you need to allocate $(textlengthcdot 2)+1$ bytes, rather than $(textlengthcdot2)$ to account for the null terminator sprintf() adds.



Formatting



Most C formatting guides do not include spaces around the arguments to function calls, nor the expressions within an if-statement. For an example of a C style most C programmers would find acceptable, see OpenBSD's style(9) manual.



I choose to associate * with the variable name, rather than floating between the type and name. This disambiguates the following example:



int *a, b;


Here, a is a pointer to an integer, but b is only an integer. By moving the asterisk next to the name, it makes this clearer.



int length = strlen ( str );
char * newStr = malloc (length * 2 );
if ( !newStr) shutDown ( "can't allocate memory" ) ;


Becomes:



int const len = strlen(str);
char *const new_str = malloc(1 + len * 2);

if (new_str == NULL)
shutDown("can't allocate memory");



Error checking



Rather than calling shutDown() and exit()ing the program, you should instead return an error value which can be checked by the caller of str_to_hex(). Because you return a pointer, you can return NULL to indicate an error occurred and the caller should check errno.



Likewise, on some systems your program can incorrectly exit when length == 0. If we look at the manual page for malloc(3):




Return Value



The malloc() and calloc() functions return a pointer to the allocated memory that is suitably aligned for any kind of variable. On error, these functions return NULL. NULL may also be returned by a successful call to malloc() with a size of zero, or by a successful call to calloc() with nmemb or size equal to zero.




So by returning NULL we account for the case where malloc(3) returns NULL on success.



if (new_str == NULL) 
shutDown("can't alloc memory");



Becomes:



if (new_str == NULL) 
return NULL;



If you choose, you can also check if str is NULL before calling strlen(). This is up to you, and it's not uncommon in C to ignore this case and leave it as user error.



Looping



Use the size_t type in your loop rather than int. size_t is guaranteed be wide enough to hold any array index, while int is not.



Using i rather than x is more common for looping variables.



The y variable isn't needed. You can simply use str[i] in its place.



In terms of performance there's likely a faster option than using sprintf(). You should look into strtol(3).



Conclusion



Here is the code I ended up with:



#include <stdio.h>
#include <stdlib.h>
#include <string.h>

char *
str_to_hex(char const *const str)

size_t const len = strlen(str);

char *const new_str = malloc(1 + len * 2);

if (new_str == NULL)
return NULL;


for (size_t i = 0; i < len; ++i)
sprintf(new_str + i * 2, "%02X", str[i]);


return new_str;


int
main(void)

char *str = "abz";
char *hex = str_to_hex(str);

if (hex == NULL && strlen(str) != 0)
/* error ... */


printf("%sn",hex);

free(hex);



Hope this helps!






share|improve this answer











$endgroup$



Bug



As Carsten points out, you need to allocate $(textlengthcdot 2)+1$ bytes, rather than $(textlengthcdot2)$ to account for the null terminator sprintf() adds.



Formatting



Most C formatting guides do not include spaces around the arguments to function calls, nor the expressions within an if-statement. For an example of a C style most C programmers would find acceptable, see OpenBSD's style(9) manual.



I choose to associate * with the variable name, rather than floating between the type and name. This disambiguates the following example:



int *a, b;


Here, a is a pointer to an integer, but b is only an integer. By moving the asterisk next to the name, it makes this clearer.



int length = strlen ( str );
char * newStr = malloc (length * 2 );
if ( !newStr) shutDown ( "can't allocate memory" ) ;


Becomes:



int const len = strlen(str);
char *const new_str = malloc(1 + len * 2);

if (new_str == NULL)
shutDown("can't allocate memory");



Error checking



Rather than calling shutDown() and exit()ing the program, you should instead return an error value which can be checked by the caller of str_to_hex(). Because you return a pointer, you can return NULL to indicate an error occurred and the caller should check errno.



Likewise, on some systems your program can incorrectly exit when length == 0. If we look at the manual page for malloc(3):




Return Value



The malloc() and calloc() functions return a pointer to the allocated memory that is suitably aligned for any kind of variable. On error, these functions return NULL. NULL may also be returned by a successful call to malloc() with a size of zero, or by a successful call to calloc() with nmemb or size equal to zero.




So by returning NULL we account for the case where malloc(3) returns NULL on success.



if (new_str == NULL) 
shutDown("can't alloc memory");



Becomes:



if (new_str == NULL) 
return NULL;



If you choose, you can also check if str is NULL before calling strlen(). This is up to you, and it's not uncommon in C to ignore this case and leave it as user error.



Looping



Use the size_t type in your loop rather than int. size_t is guaranteed be wide enough to hold any array index, while int is not.



Using i rather than x is more common for looping variables.



The y variable isn't needed. You can simply use str[i] in its place.



In terms of performance there's likely a faster option than using sprintf(). You should look into strtol(3).



Conclusion



Here is the code I ended up with:



#include <stdio.h>
#include <stdlib.h>
#include <string.h>

char *
str_to_hex(char const *const str)

size_t const len = strlen(str);

char *const new_str = malloc(1 + len * 2);

if (new_str == NULL)
return NULL;


for (size_t i = 0; i < len; ++i)
sprintf(new_str + i * 2, "%02X", str[i]);


return new_str;


int
main(void)

char *str = "abz";
char *hex = str_to_hex(str);

if (hex == NULL && strlen(str) != 0)
/* error ... */


printf("%sn",hex);

free(hex);



Hope this helps!







share|improve this answer














share|improve this answer



share|improve this answer








edited 15 hours ago

























answered yesterday









esoteesote

3,01411039




3,01411039







  • 1




    $begingroup$
    Won't printf() require hex to have a trailing byte?
    $endgroup$
    – jochen
    21 hours ago






  • 3




    $begingroup$
    You should allocate 2*len+1 bytes.
    $endgroup$
    – Carsten S
    20 hours ago










  • $begingroup$
    Good advice but it fails to fix the bug in OP’s code.
    $endgroup$
    – Konrad Rudolph
    15 hours ago










  • $begingroup$
    sprintf adds a null terminator. @Carsten thanks, I forgot to include that, I'll update my answer
    $endgroup$
    – esote
    15 hours ago






  • 1




    $begingroup$
    @Accountantم It is from the OpenBSD manual, the style is called BSD kernel normal form (KNF). Around the middle of manual: "The function type should be on a line by itself preceding the function."
    $endgroup$
    – esote
    12 hours ago













  • 1




    $begingroup$
    Won't printf() require hex to have a trailing byte?
    $endgroup$
    – jochen
    21 hours ago






  • 3




    $begingroup$
    You should allocate 2*len+1 bytes.
    $endgroup$
    – Carsten S
    20 hours ago










  • $begingroup$
    Good advice but it fails to fix the bug in OP’s code.
    $endgroup$
    – Konrad Rudolph
    15 hours ago










  • $begingroup$
    sprintf adds a null terminator. @Carsten thanks, I forgot to include that, I'll update my answer
    $endgroup$
    – esote
    15 hours ago






  • 1




    $begingroup$
    @Accountantم It is from the OpenBSD manual, the style is called BSD kernel normal form (KNF). Around the middle of manual: "The function type should be on a line by itself preceding the function."
    $endgroup$
    – esote
    12 hours ago








1




1




$begingroup$
Won't printf() require hex to have a trailing byte?
$endgroup$
– jochen
21 hours ago




$begingroup$
Won't printf() require hex to have a trailing byte?
$endgroup$
– jochen
21 hours ago




3




3




$begingroup$
You should allocate 2*len+1 bytes.
$endgroup$
– Carsten S
20 hours ago




$begingroup$
You should allocate 2*len+1 bytes.
$endgroup$
– Carsten S
20 hours ago












$begingroup$
Good advice but it fails to fix the bug in OP’s code.
$endgroup$
– Konrad Rudolph
15 hours ago




$begingroup$
Good advice but it fails to fix the bug in OP’s code.
$endgroup$
– Konrad Rudolph
15 hours ago












$begingroup$
sprintf adds a null terminator. @Carsten thanks, I forgot to include that, I'll update my answer
$endgroup$
– esote
15 hours ago




$begingroup$
sprintf adds a null terminator. @Carsten thanks, I forgot to include that, I'll update my answer
$endgroup$
– esote
15 hours ago




1




1




$begingroup$
@Accountantم It is from the OpenBSD manual, the style is called BSD kernel normal form (KNF). Around the middle of manual: "The function type should be on a line by itself preceding the function."
$endgroup$
– esote
12 hours ago





$begingroup$
@Accountantم It is from the OpenBSD manual, the style is called BSD kernel normal form (KNF). Around the middle of manual: "The function type should be on a line by itself preceding the function."
$endgroup$
– esote
12 hours ago














2












$begingroup$

In my opinion, the most severe problem is "Insufficient target memory".



int length = strlen ( str );
char * newStr = malloc( length * 2 );


You are allocating twice the length of str, which is enough for all the hex characters (two hex chars per input byte).



But sprintf works different: "A terminating null character is automatically appended after the content" (see here).



So the last call to sprintf will write a terminating zero byte right after newStr, into unallocated memory. This might provoke all kinds of unintended behaviour, including (but not limited to) crashes.






share|improve this answer









$endgroup$












  • $begingroup$
    Yes thank you, it's a bug. I forgot to terminate newStr, thanks for highlighting this as it's the biggest problem in my code.
    $endgroup$
    – Accountant م
    14 hours ago















2












$begingroup$

In my opinion, the most severe problem is "Insufficient target memory".



int length = strlen ( str );
char * newStr = malloc( length * 2 );


You are allocating twice the length of str, which is enough for all the hex characters (two hex chars per input byte).



But sprintf works different: "A terminating null character is automatically appended after the content" (see here).



So the last call to sprintf will write a terminating zero byte right after newStr, into unallocated memory. This might provoke all kinds of unintended behaviour, including (but not limited to) crashes.






share|improve this answer









$endgroup$












  • $begingroup$
    Yes thank you, it's a bug. I forgot to terminate newStr, thanks for highlighting this as it's the biggest problem in my code.
    $endgroup$
    – Accountant م
    14 hours ago













2












2








2





$begingroup$

In my opinion, the most severe problem is "Insufficient target memory".



int length = strlen ( str );
char * newStr = malloc( length * 2 );


You are allocating twice the length of str, which is enough for all the hex characters (two hex chars per input byte).



But sprintf works different: "A terminating null character is automatically appended after the content" (see here).



So the last call to sprintf will write a terminating zero byte right after newStr, into unallocated memory. This might provoke all kinds of unintended behaviour, including (but not limited to) crashes.






share|improve this answer









$endgroup$



In my opinion, the most severe problem is "Insufficient target memory".



int length = strlen ( str );
char * newStr = malloc( length * 2 );


You are allocating twice the length of str, which is enough for all the hex characters (two hex chars per input byte).



But sprintf works different: "A terminating null character is automatically appended after the content" (see here).



So the last call to sprintf will write a terminating zero byte right after newStr, into unallocated memory. This might provoke all kinds of unintended behaviour, including (but not limited to) crashes.







share|improve this answer












share|improve this answer



share|improve this answer










answered 15 hours ago









jvbjvb

879210




879210











  • $begingroup$
    Yes thank you, it's a bug. I forgot to terminate newStr, thanks for highlighting this as it's the biggest problem in my code.
    $endgroup$
    – Accountant م
    14 hours ago
















  • $begingroup$
    Yes thank you, it's a bug. I forgot to terminate newStr, thanks for highlighting this as it's the biggest problem in my code.
    $endgroup$
    – Accountant م
    14 hours ago















$begingroup$
Yes thank you, it's a bug. I forgot to terminate newStr, thanks for highlighting this as it's the biggest problem in my code.
$endgroup$
– Accountant م
14 hours ago




$begingroup$
Yes thank you, it's a bug. I forgot to terminate newStr, thanks for highlighting this as it's the biggest problem in my code.
$endgroup$
– Accountant م
14 hours ago











1












$begingroup$

Just one addition: like asprintf vs snprintf. One can effectively predict the size, so I would think it natural to have a string buffer and the size passed in instead of creating it dynamically.



#include <stdlib.h> /* strtol */
#include <string.h> /* strlen */
#include <stdio.h> /* printf */
#include <assert.h> /* assert */

/** Converts str to the underlying bit representation in hex, stored in
hex. It may fail to compute the entire string due to hex_size, in which
case the return will be less then the str length.
str: A valid null-terminated string.
hex: The output string.
hex_size: The output string's size.
return: The number of characters from the original that it processed. */
static size_t strToHex(const char *str, char *hex, size_t hex_size)

static const char digits[0x0F] = '0', '1', '2', '3', '4', '5',
'6', '7', '8', '9', 'A', 'B', 'C', 'E', 'F' ;
const size_t str_len = strlen(str), hex_len = hex_size - 1;
const size_t length = str_len < hex_len / 2 ? str_len : hex_len / 2;
const char *s = str;
char *h = hex;
size_t x;
assert(str && hex);
if(!hex_size) return 0;
for(x = 0; x < length; x++)
*h++ = digits[(*s & 0xF0) >> 4], *h++ = digits[*s++ & 0x0F];
*h = '';
return s - str;


int main(void)

const char *str = "abcdefghijklmnopqrstuvwxyz", *str2 = "æôƌԹظⓐa";
char hex[80];
size_t ret;
ret = strToHex(str, hex, sizeof hex);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str, hex, sizeof hex / 2);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str, hex, 0);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str2, hex, sizeof hex);
printf(""%s" -> "%s" (%lu.)n", str2, hex, (unsigned long)ret);
return EXIT_SUCCESS;



It cannot really fail if given the proper input, so this simplifies error checking a lot, especially in C. malloc and sprintf are pretty slow functions, comparatively, so I expect this to be faster and more robust.






share|improve this answer











$endgroup$












  • $begingroup$
    Thank you very much, I like the way you documented the function, is this a known convention for documenting C code ? I also like the performance consideration that this function has over the function I posted, but I generally give easier user interfaces more priority over performance, unless I get bottlenecks. I will study your code today again with a deeper look.
    $endgroup$
    – Accountant م
    14 hours ago















1












$begingroup$

Just one addition: like asprintf vs snprintf. One can effectively predict the size, so I would think it natural to have a string buffer and the size passed in instead of creating it dynamically.



#include <stdlib.h> /* strtol */
#include <string.h> /* strlen */
#include <stdio.h> /* printf */
#include <assert.h> /* assert */

/** Converts str to the underlying bit representation in hex, stored in
hex. It may fail to compute the entire string due to hex_size, in which
case the return will be less then the str length.
str: A valid null-terminated string.
hex: The output string.
hex_size: The output string's size.
return: The number of characters from the original that it processed. */
static size_t strToHex(const char *str, char *hex, size_t hex_size)

static const char digits[0x0F] = '0', '1', '2', '3', '4', '5',
'6', '7', '8', '9', 'A', 'B', 'C', 'E', 'F' ;
const size_t str_len = strlen(str), hex_len = hex_size - 1;
const size_t length = str_len < hex_len / 2 ? str_len : hex_len / 2;
const char *s = str;
char *h = hex;
size_t x;
assert(str && hex);
if(!hex_size) return 0;
for(x = 0; x < length; x++)
*h++ = digits[(*s & 0xF0) >> 4], *h++ = digits[*s++ & 0x0F];
*h = '';
return s - str;


int main(void)

const char *str = "abcdefghijklmnopqrstuvwxyz", *str2 = "æôƌԹظⓐa";
char hex[80];
size_t ret;
ret = strToHex(str, hex, sizeof hex);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str, hex, sizeof hex / 2);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str, hex, 0);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str2, hex, sizeof hex);
printf(""%s" -> "%s" (%lu.)n", str2, hex, (unsigned long)ret);
return EXIT_SUCCESS;



It cannot really fail if given the proper input, so this simplifies error checking a lot, especially in C. malloc and sprintf are pretty slow functions, comparatively, so I expect this to be faster and more robust.






share|improve this answer











$endgroup$












  • $begingroup$
    Thank you very much, I like the way you documented the function, is this a known convention for documenting C code ? I also like the performance consideration that this function has over the function I posted, but I generally give easier user interfaces more priority over performance, unless I get bottlenecks. I will study your code today again with a deeper look.
    $endgroup$
    – Accountant م
    14 hours ago













1












1








1





$begingroup$

Just one addition: like asprintf vs snprintf. One can effectively predict the size, so I would think it natural to have a string buffer and the size passed in instead of creating it dynamically.



#include <stdlib.h> /* strtol */
#include <string.h> /* strlen */
#include <stdio.h> /* printf */
#include <assert.h> /* assert */

/** Converts str to the underlying bit representation in hex, stored in
hex. It may fail to compute the entire string due to hex_size, in which
case the return will be less then the str length.
str: A valid null-terminated string.
hex: The output string.
hex_size: The output string's size.
return: The number of characters from the original that it processed. */
static size_t strToHex(const char *str, char *hex, size_t hex_size)

static const char digits[0x0F] = '0', '1', '2', '3', '4', '5',
'6', '7', '8', '9', 'A', 'B', 'C', 'E', 'F' ;
const size_t str_len = strlen(str), hex_len = hex_size - 1;
const size_t length = str_len < hex_len / 2 ? str_len : hex_len / 2;
const char *s = str;
char *h = hex;
size_t x;
assert(str && hex);
if(!hex_size) return 0;
for(x = 0; x < length; x++)
*h++ = digits[(*s & 0xF0) >> 4], *h++ = digits[*s++ & 0x0F];
*h = '';
return s - str;


int main(void)

const char *str = "abcdefghijklmnopqrstuvwxyz", *str2 = "æôƌԹظⓐa";
char hex[80];
size_t ret;
ret = strToHex(str, hex, sizeof hex);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str, hex, sizeof hex / 2);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str, hex, 0);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str2, hex, sizeof hex);
printf(""%s" -> "%s" (%lu.)n", str2, hex, (unsigned long)ret);
return EXIT_SUCCESS;



It cannot really fail if given the proper input, so this simplifies error checking a lot, especially in C. malloc and sprintf are pretty slow functions, comparatively, so I expect this to be faster and more robust.






share|improve this answer











$endgroup$



Just one addition: like asprintf vs snprintf. One can effectively predict the size, so I would think it natural to have a string buffer and the size passed in instead of creating it dynamically.



#include <stdlib.h> /* strtol */
#include <string.h> /* strlen */
#include <stdio.h> /* printf */
#include <assert.h> /* assert */

/** Converts str to the underlying bit representation in hex, stored in
hex. It may fail to compute the entire string due to hex_size, in which
case the return will be less then the str length.
str: A valid null-terminated string.
hex: The output string.
hex_size: The output string's size.
return: The number of characters from the original that it processed. */
static size_t strToHex(const char *str, char *hex, size_t hex_size)

static const char digits[0x0F] = '0', '1', '2', '3', '4', '5',
'6', '7', '8', '9', 'A', 'B', 'C', 'E', 'F' ;
const size_t str_len = strlen(str), hex_len = hex_size - 1;
const size_t length = str_len < hex_len / 2 ? str_len : hex_len / 2;
const char *s = str;
char *h = hex;
size_t x;
assert(str && hex);
if(!hex_size) return 0;
for(x = 0; x < length; x++)
*h++ = digits[(*s & 0xF0) >> 4], *h++ = digits[*s++ & 0x0F];
*h = '';
return s - str;


int main(void)

const char *str = "abcdefghijklmnopqrstuvwxyz", *str2 = "æôƌԹظⓐa";
char hex[80];
size_t ret;
ret = strToHex(str, hex, sizeof hex);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str, hex, sizeof hex / 2);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str, hex, 0);
printf(""%s" -> "%s" (%lu.)n", str, hex, (unsigned long)ret);
ret = strToHex(str2, hex, sizeof hex);
printf(""%s" -> "%s" (%lu.)n", str2, hex, (unsigned long)ret);
return EXIT_SUCCESS;



It cannot really fail if given the proper input, so this simplifies error checking a lot, especially in C. malloc and sprintf are pretty slow functions, comparatively, so I expect this to be faster and more robust.







share|improve this answer














share|improve this answer



share|improve this answer








edited yesterday

























answered yesterday









Neil EdelmanNeil Edelman

317110




317110











  • $begingroup$
    Thank you very much, I like the way you documented the function, is this a known convention for documenting C code ? I also like the performance consideration that this function has over the function I posted, but I generally give easier user interfaces more priority over performance, unless I get bottlenecks. I will study your code today again with a deeper look.
    $endgroup$
    – Accountant م
    14 hours ago
















  • $begingroup$
    Thank you very much, I like the way you documented the function, is this a known convention for documenting C code ? I also like the performance consideration that this function has over the function I posted, but I generally give easier user interfaces more priority over performance, unless I get bottlenecks. I will study your code today again with a deeper look.
    $endgroup$
    – Accountant م
    14 hours ago















$begingroup$
Thank you very much, I like the way you documented the function, is this a known convention for documenting C code ? I also like the performance consideration that this function has over the function I posted, but I generally give easier user interfaces more priority over performance, unless I get bottlenecks. I will study your code today again with a deeper look.
$endgroup$
– Accountant م
14 hours ago




$begingroup$
Thank you very much, I like the way you documented the function, is this a known convention for documenting C code ? I also like the performance consideration that this function has over the function I posted, but I generally give easier user interfaces more priority over performance, unless I get bottlenecks. I will study your code today again with a deeper look.
$endgroup$
– Accountant م
14 hours ago











0












$begingroup$

I did more tests on the function today and found another Bug (shame on me), and AFAIK on code review I can't change the original code in the question since it got reviews.



if there are bytes have values more than 127 it will be all displayed as FF by the function. To reproduce



char str[] = 127,0;
char * hex = strToHex(str);
printf("%sn",hex); //pritnts 7F (NORMAL)

//now try with this
char str[] = 128,0;
char * hex = strToHex(str);
printf("%sn",hex); //pritnts FF (BUG)


It appears if the function is used with non English characters because they are stored with the most significant bit is set 1 in UTF-8



The Fix



To Fix it, replace this line



sprintf ( newStr + x * 2, "%02X", y );


with this



sprintf ( newStr + x * 2, "%02hhX", y ); // added hh


This is because y is of type char or signed char and the X specifier expects the argument to be unsigned int if no length is provided, so we provided length hh to tell the function that X is unsigned char . Check the length table of printf.



If we didn't provided hh, the sprintf function is going to promote Y from signed char to unsigned int and this promotion will go like this



when we defined the str as char and assigned the value 128 to it, it's represented as



1000 0000


The compiler thought it is -128 because it's type is signed char, now function sprintf wants to promote it to unsigned int, so to represent -128 in size of int, it will be like



1111 1111 1111 1111 1111 1111 1000 0000
^^^^ ^^^^ ^^^^ ^^^^


and because we chose to show only 2 digits then we see the last 2 bytes FF.



more info are here , and here






share|improve this answer









$endgroup$








  • 1




    $begingroup$
    This is only an issue on implementations that treat char as signed. If a char is unsigned it isn't a problem. Other possible fixes include declaring y as an unsigned char, casting y to an unsigned char in the sprintf call, or masking it (y & 0xFF).
    $endgroup$
    – 1201ProgramAlarm
    4 hours ago















0












$begingroup$

I did more tests on the function today and found another Bug (shame on me), and AFAIK on code review I can't change the original code in the question since it got reviews.



if there are bytes have values more than 127 it will be all displayed as FF by the function. To reproduce



char str[] = 127,0;
char * hex = strToHex(str);
printf("%sn",hex); //pritnts 7F (NORMAL)

//now try with this
char str[] = 128,0;
char * hex = strToHex(str);
printf("%sn",hex); //pritnts FF (BUG)


It appears if the function is used with non English characters because they are stored with the most significant bit is set 1 in UTF-8



The Fix



To Fix it, replace this line



sprintf ( newStr + x * 2, "%02X", y );


with this



sprintf ( newStr + x * 2, "%02hhX", y ); // added hh


This is because y is of type char or signed char and the X specifier expects the argument to be unsigned int if no length is provided, so we provided length hh to tell the function that X is unsigned char . Check the length table of printf.



If we didn't provided hh, the sprintf function is going to promote Y from signed char to unsigned int and this promotion will go like this



when we defined the str as char and assigned the value 128 to it, it's represented as



1000 0000


The compiler thought it is -128 because it's type is signed char, now function sprintf wants to promote it to unsigned int, so to represent -128 in size of int, it will be like



1111 1111 1111 1111 1111 1111 1000 0000
^^^^ ^^^^ ^^^^ ^^^^


and because we chose to show only 2 digits then we see the last 2 bytes FF.



more info are here , and here






share|improve this answer









$endgroup$








  • 1




    $begingroup$
    This is only an issue on implementations that treat char as signed. If a char is unsigned it isn't a problem. Other possible fixes include declaring y as an unsigned char, casting y to an unsigned char in the sprintf call, or masking it (y & 0xFF).
    $endgroup$
    – 1201ProgramAlarm
    4 hours ago













0












0








0





$begingroup$

I did more tests on the function today and found another Bug (shame on me), and AFAIK on code review I can't change the original code in the question since it got reviews.



if there are bytes have values more than 127 it will be all displayed as FF by the function. To reproduce



char str[] = 127,0;
char * hex = strToHex(str);
printf("%sn",hex); //pritnts 7F (NORMAL)

//now try with this
char str[] = 128,0;
char * hex = strToHex(str);
printf("%sn",hex); //pritnts FF (BUG)


It appears if the function is used with non English characters because they are stored with the most significant bit is set 1 in UTF-8



The Fix



To Fix it, replace this line



sprintf ( newStr + x * 2, "%02X", y );


with this



sprintf ( newStr + x * 2, "%02hhX", y ); // added hh


This is because y is of type char or signed char and the X specifier expects the argument to be unsigned int if no length is provided, so we provided length hh to tell the function that X is unsigned char . Check the length table of printf.



If we didn't provided hh, the sprintf function is going to promote Y from signed char to unsigned int and this promotion will go like this



when we defined the str as char and assigned the value 128 to it, it's represented as



1000 0000


The compiler thought it is -128 because it's type is signed char, now function sprintf wants to promote it to unsigned int, so to represent -128 in size of int, it will be like



1111 1111 1111 1111 1111 1111 1000 0000
^^^^ ^^^^ ^^^^ ^^^^


and because we chose to show only 2 digits then we see the last 2 bytes FF.



more info are here , and here






share|improve this answer









$endgroup$



I did more tests on the function today and found another Bug (shame on me), and AFAIK on code review I can't change the original code in the question since it got reviews.



if there are bytes have values more than 127 it will be all displayed as FF by the function. To reproduce



char str[] = 127,0;
char * hex = strToHex(str);
printf("%sn",hex); //pritnts 7F (NORMAL)

//now try with this
char str[] = 128,0;
char * hex = strToHex(str);
printf("%sn",hex); //pritnts FF (BUG)


It appears if the function is used with non English characters because they are stored with the most significant bit is set 1 in UTF-8



The Fix



To Fix it, replace this line



sprintf ( newStr + x * 2, "%02X", y );


with this



sprintf ( newStr + x * 2, "%02hhX", y ); // added hh


This is because y is of type char or signed char and the X specifier expects the argument to be unsigned int if no length is provided, so we provided length hh to tell the function that X is unsigned char . Check the length table of printf.



If we didn't provided hh, the sprintf function is going to promote Y from signed char to unsigned int and this promotion will go like this



when we defined the str as char and assigned the value 128 to it, it's represented as



1000 0000


The compiler thought it is -128 because it's type is signed char, now function sprintf wants to promote it to unsigned int, so to represent -128 in size of int, it will be like



1111 1111 1111 1111 1111 1111 1000 0000
^^^^ ^^^^ ^^^^ ^^^^


and because we chose to show only 2 digits then we see the last 2 bytes FF.



more info are here , and here







share|improve this answer












share|improve this answer



share|improve this answer










answered 4 hours ago









Accountant مAccountant م

22418




22418







  • 1




    $begingroup$
    This is only an issue on implementations that treat char as signed. If a char is unsigned it isn't a problem. Other possible fixes include declaring y as an unsigned char, casting y to an unsigned char in the sprintf call, or masking it (y & 0xFF).
    $endgroup$
    – 1201ProgramAlarm
    4 hours ago












  • 1




    $begingroup$
    This is only an issue on implementations that treat char as signed. If a char is unsigned it isn't a problem. Other possible fixes include declaring y as an unsigned char, casting y to an unsigned char in the sprintf call, or masking it (y & 0xFF).
    $endgroup$
    – 1201ProgramAlarm
    4 hours ago







1




1




$begingroup$
This is only an issue on implementations that treat char as signed. If a char is unsigned it isn't a problem. Other possible fixes include declaring y as an unsigned char, casting y to an unsigned char in the sprintf call, or masking it (y & 0xFF).
$endgroup$
– 1201ProgramAlarm
4 hours ago




$begingroup$
This is only an issue on implementations that treat char as signed. If a char is unsigned it isn't a problem. Other possible fixes include declaring y as an unsigned char, casting y to an unsigned char in the sprintf call, or masking it (y & 0xFF).
$endgroup$
– 1201ProgramAlarm
4 hours ago

















draft saved

draft discarded
















































Thanks for contributing an answer to Code Review Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

Use MathJax to format equations. MathJax reference.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f216992%2fstrtohex-string-to-its-hex-representation-as-string%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Category:9 (number) SubcategoriesMedia in category "9 (number)"Navigation menuUpload mediaGND ID: 4485639-8Library of Congress authority ID: sh85091979ReasonatorScholiaStatistics

Circuit construction for execution of conditional statements using least significant bitHow are two different registers being used as “control”?How exactly is the stated composite state of the two registers being produced using the $R_zz$ controlled rotations?Efficiently performing controlled rotations in HHLWould this quantum algorithm implementation work?How to prepare a superposed states of odd integers from $1$ to $sqrtN$?Why is this implementation of the order finding algorithm not working?Circuit construction for Hamiltonian simulationHow can I invert the least significant bit of a certain term of a superposed state?Implementing an oracleImplementing a controlled sum operation

Magento 2 “No Payment Methods” in Admin New OrderHow to integrate Paypal Express Checkout with the Magento APIMagento 1.5 - Sales > Order > edit order and shipping methods disappearAuto Invoice Check/Money Order Payment methodAdd more simple payment methods?Shipping methods not showingWhat should I do to change payment methods if changing the configuration has no effects?1.9 - No Payment Methods showing upMy Payment Methods not Showing for downloadable/virtual product when checkout?Magento2 API to access internal payment methodHow to call an existing payment methods in the registration form?