strcpy() related segmentation fault

Question

my problem is i have a program that runs on Windows perfectly while on Dev machine it gives segmentation fault without any output from my program.To test it ,i put a printf() at the start of main ,before any code piece and it still gave segmentaion fault without printing anything.

#0 0x00007f374105adc0 in __strcpy_sse2 () from /lib64/libc.so.6

Only line is understandable by me is above bolded line.I did not want to bloat page with my whole code .So if you can give me a direction or ask for specific lines,i will be ready here.

Edit:Added meaningful backtrace,removed some mumbo jumbo. I investigated debugging a bit more and reached these info;

0 0x00007f6da93f2dc0 in __strcpy_sse2 () from /lib64/libc.so.6

1 0x00000000004017e5 in read_customer_info ()

2 0x0000000000401756 in read_customers ()

3 0x0000000000401289 in operate ()

4 0x0000000000401a64 in main ()

code piece in the innermost function ;

char *name;
name = (char*)malloc(15*sizeof(char));
int transaction_amount;
int transaction_time;

coming_minute=atoi(strtok(temp_line,",\0"));
strcpy(name,strtok(NULL,",\0"));

I can see using strtok as argument of strcpy might cause this segfault.Should i use temporary char pointer instead of directly using the one from strtok() return value?

The best thing you can do is create a minimum working example. Don't post the whole code, just a couple of lines that showcase the problem. You'd be surprised if you don't find the error yourself while constructing the example :-) — Fredrik Pihl, Dec 09 '13 at 20:16
You pass a valid format string into `printf`, e.g. `printf("abc")`, don't you? — Maxim Egorushkin, Dec 09 '13 at 20:39
This isn't enough information. Usually if you see a crash in strcpy it means bad inputs. You have to use the "up" command to go up the stack to find the error — Tom Tromey, Dec 09 '13 at 23:39

strcpy() related segmentation fault

0 Answers0