5.1.21 · D1Safe alternatives — strncpy, snprintf, strlcpy
Intuition Ek core idea jo sabse zaroori haiC ki ek "string" memory mein sirf bytes ki ek row hoti hai jo ek special marker byte — '\0' — pe khatam hoti hai; usme koi stored length nahi hoti , isliye har string function aage chalte rehta hai jab tak woh marker nahi milta . Safe copying ki poori baat ek hi sawaal hai: kya meri destination row mein copy AND uska ending marker dono ke liye kaafi bytes hain, aur walk edge se bahar jaane se pehle ruk jaayegi?
Isse pehle ki tum strncpy, snprintf, ya strlcpy samjho, tumhe yeh dikhna chahiye ki C string memory mein actually kaisi hoti hai. Parent note mein char buf[8], '\0', sizeof, size, aur "off the end" aise use kiya gaya hai jaise yeh sab obvious ho. Yeh page inhe ek-ek karke, kuch nahi se, earn karta hai.
char
Ek byte memory ka sabse chhota addressable chunk hai — ise ek tiny numbered box samjho jo ek number (0–255) hold karta hai. C mein, type char hai hi ek byte. Ek single letter jaise 'h' uske number code ke roop mein store hota hai (for 'h' woh number hai 104).
Puri topic ke liye tumhare dimaag mein yeh picture rehni chahiye: memory ek lambi strip of numbered boxes hai, aur har box ek number hold karta hai jise hum ek letter ki tarah padh sakte hain.
Intuition Boxes kyun, letters kyun nahiComputer kabhi "letters" store nahi karta. Woh boxes mein numbers store karta hai. Koi box h letter "hai" ya number 104, yeh sirf is baat par depend karta hai ki hum use kaise padhna choose karte hain . Isliye ek stray byte silently garbage text ban sakta hai — wahi box, alag reading.
char buf[8]
Yeh exactly 8 consecutive boxes reserve karta hai aur poori row ko buf naam deta hai. Individual boxes hain buf[0], buf[1], …, buf[7]. Index counting 0 se shuru hoti hai, isliye aakhri legal box hai buf[7], buf[8] nahi.
Common mistake Shuru se hi off-by-oneYeh galat kyun lagta hai: size 8 hai, toh pakka buf[8] exist karta hoga? Nahi. 0 se number hue 8 boxes hain 0..7. buf[8] 9th box hai — woh buf ki nahi hai. Use touch karna exactly wahi "walk off the end" hai jiske baare mein poori topic hai.
Dhyan do ki buf mein kuch bhi built-in nahi jo kahe "meri length 8 hai." Number 8 sirf tumhare source code mein hai, memory mein nahi. Yahi missing length hai jo C string functions ko dangerous banati hai — dekho C strings and the null terminator .
Definition Null terminator'\0'
'\0' ek single char hai jiska stored number 0 (zero) hai. Yeh digit '0' nahi hai (jiska number 48 hai). C yeh zero-byte ek signpost ki tarah use karta hai jiska matlab hai "string yahaan khatam hoti hai."
Yeh poori topic ka sabse important symbol hai. C mein ek "string" define hoti hai is tarah:
Intuition Stored length ki jagah marker kyun?Kyunki C strings mein koi length field nahi hoti . strlen jaisi function length is tarah dhoondti hai: box 0 se shuru karke right chalte jaao jab tak '\0' nahi milta . Marker hatao aur walk kabhi rukti nahi — woh box ke baad box padhta rehta hai, unrelated memory mein. Yahi woh runaway walk hai jo parent note mein strncpy ka failure mode hai. Deep dive: sizeof vs strlen .
sizeof(buf)
sizeof(buf) array ke liye reserve ki gayi boxes ki total sankhya hai — capacity ke baare mein ek compile-time fact. char buf[8] ke liye yeh 8 hai, chahe boxes filled hoon ya nahi.
strlen(buf)
strlen(buf) =='\0' se pehle ke visible characters count== karta hai — yeh run time par row ko walk karta hai. Yeh '\0' ko khud count nahi karta.
Worked example Same buffer, do alag numberschar buf [ 8 ]; strcpy (buf, "hi" ); // fills 'h' 'i' '\0' // sizeof(buf) == 8 (capacity — kabhi nahi badlti) // strlen(buf) == 2 (content — marker tak) Marker ke baad ke 5 boxes abhi bhi exist karte hain (capacity 8) lekin jo bhi junk pehle tha woh rakhte hain.
dest aur src
Har copy function ek destination (dest, jahan bytes likhi jaati hain) aur ek source (src, jahan se bytes padhi jaati hain) leta hai. Paani src → dest ki taraf behta hai. Overflow hamesha ek dest problem hai: dest itna chhota hai ki src jo daal raha hai woh nahin samata.
size_t
Yeh "kitna bada" argument ka type hai. Yeh sirf ek unsigned (non-negative) whole number hai jo sizes aur counts ke liye use hota hai. Jab tum size_t r = strlcpy(...) dekhte ho, r sirf characters ka ek count hai — kuch exotic nahi.
Ek function finish hone par ek number wapas de sakta hai. Parent note is par bahut depend karta hai: snprintf aur strlcpy return karte hain "kitne characters main chahta tha ," jise tum truncation detect karne ke liye capacity se compare karte ho.
Ab parent note ka opening example khud padha jaata hai:
char buf [ 8 ]; strcpy (buf, "hello world" ); // 12 chars → needs 13 boxes "hello world" ko 11 + 1 = 12 buf mein sirf 8 hain. strcpy ko sizeof(buf) ki koi jaankari ya check nahi hota, isliye woh box 7 ke baad boxes 8, 9, 10… mein likhta rehta hai — jo doosri cheezoon ki hain — yahi hai Buffer overflow and stack smashing aur Memory safety and undefined behavior ka essence.
char buf 8 is a row of boxes
Null terminator marks the end
A C string is boxes plus marker
strlen must be at most sizeof minus 1
Overflow walks off the row
Safe alternatives strncpy snprintf strlcpy
char buf[8] kitne boxes reserve karta hai, aur aakhri legal index kya hai?8 boxes; aakhri legal index hai buf[7] (indexing 0 se shuru hoti hai).
'\0' byte mein kaunsa number stored hota hai, aur yeh '0' se alag kaise hai?'\0' mein 0 store hota hai; '0' mein 48 — yeh bilkul alag bytes hain.
k visible characters store karne ke liye k+1 boxes kyun chahiye?'\0' end-marker ke liye ek extra box chahiye hota hai.
sizeof(buf) kya measure karta hai versus strlen(buf)?sizeof = total capacity in bytes (compile-time); strlen = '\0' tak visible characters (run time par walk karke).
Content aur capacity ko relate karne wali safety inequality batao. strlen(buf) <= sizeof(buf) - 1.
Agar C mein koi length store nahi hoti toh string function "jaanta" kaise hai ki string kahan khatam hoti hai? Woh box 0 se aage chalta rehta hai jab tak '\0' byte nahi milta.
copy(dest, src, size) mein kaunsi side overflow ho sakti hai aur kyun?dest — yeh itna chhota ho sakta hai ki src jo daal raha hai woh na samaye.
Truncation detect karne ka ek-line rule batao. Truncation tab hua jab return >= size.
Parent: Safe alternatives C strings and the null terminator sizeof vs strlen strcpy and sprintf (unsafe) Buffer overflow and stack smashing Memory safety and undefined behavior Format strings and printf family 
