Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
http://d.pr/f/FIjf
Please check up main.c. I assigned a string as char *s3 = "0,9,8,7,6,5,4,3,2,1"; and there will be a SIGSEGV at running. When I de-annotate this line, then there is no SIGSEGV. So why does this string assignment lead to SIGSEGV?
Most likely you are modifying a string literal resulting in Undefined Behavior(UB).
s3points to a string literal stored in read only implementation defined memory and any attempt to modify this string literal results in Undefined Behavior. In fact you are lucky that your code crashes because UB does not necessarily mandate a crash, but it can give you weird or literally any result.