Its printing garbage can you please help meCode:char *str2;
char *first1 = "Learn";
char *second1 = "C";
char *third1 = "Online";
str2=(char *)malloc(strlen(first1)+strlen(second1)+strlen(third1)+3);
sprintf(str2, "%s %s %s",first,second,third);
puts(str2);
Post something which compiles!
When typos are fixed, there is nothing wrong with the code - save for the memory leak at the end.Code:$ gcc -Wall bar.c
bar.c: In function ‘main’:
bar.c:12:26: error: ‘first’ undeclared (first use in this function)
bar.c:12:26: note: each undeclared identifier is reported only once for each function it appears in
bar.c:12:32: error: ‘second’ undeclared (first use in this function)
bar.c:12:39: error: ‘third’ undeclared (first use in this function)
$
$
$ gcc -Wall bar.c
$ ./a.out
Learn C Online
$ valgrind ./a.out
==6252== Memcheck, a memory error detector
==6252== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==6252== Using Valgrind-3.6.1-Debian and LibVEX; rerun with -h for copyright info
==6252== Command: ./a.out
==6252==
Learn C Online
==6252==
==6252== HEAP SUMMARY:
==6252== in use at exit: 15 bytes in 1 blocks
==6252== total heap usage: 1 allocs, 0 frees, 15 bytes allocated
==6252==
==6252== LEAK SUMMARY:
==6252== definitely lost: 15 bytes in 1 blocks
==6252== indirectly lost: 0 bytes in 0 blocks
==6252== possibly lost: 0 bytes in 0 blocks
==6252== still reachable: 0 bytes in 0 blocks
==6252== suppressed: 0 bytes in 0 blocks
==6252== Rerun with --leak-check=full to see details of leaked memory
==6252==
==6252== For counts of detected and suppressed errors, rerun with: -v
==6252== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)