为何char指针数组输入字符串时scanf失效？运行代码报错是否操作有误？

Hey there! I totally get how confusing these little kinks can be when you're just starting out with C. Let's walk through your two problems step by step.

1. Why scanf Isn't Working with a Char Pointer Array #

The most common culprit here is unallocated memory. When you declare a char pointer array like char *strings[5];, each element in the array is just a pointer—they don't point to any actual memory space where you can store the input strings. Using scanf("%s", strings[i]) directly will write data to a random memory location, which leads to undefined behavior (it might crash, or just act weird).

Here are two easy fixes:

• Option 1: Use a 2D char array (great if you know the maximum length of your strings upfront):

  #include <stdio.h>
  
  int main() {
      char strings[5][100]; // 5 strings, each up to 99 characters + null terminator
      for (int i = 0; i < 5; i++) {
          printf("Enter string %d: ", i+1);
          scanf("%99s", strings[i]); // Limit input to 99 chars to avoid overflow
      }
      // Print them back to test
      for (int i = 0; i < 5; i++) {
          printf("String %d: %s\n", i+1, strings[i]);
      }
      return 0;
  }
  

• Option 2: Allocate memory for each pointer (more flexible if string lengths vary):

  #include <stdio.h>
  #include <stdlib.h>
  
  int main() {
      char *strings[5];
      for (int i = 0; i < 5; i++) {
          strings[i] = malloc(100 * sizeof(char)); // Allocate 100 bytes per string
          if (strings[i] == NULL) {
              printf("Memory allocation failed!\n");
              return 1;
          }
          printf("Enter string %d: ", i+1);
          scanf("%99s", strings[i]);
      }
      // Print and free memory
      for (int i = 0; i < 5; i++) {
          printf("String %d: %s\n", i+1, strings[i]);
          free(strings[i]); // Don't forget to free allocated memory!
      }
      return 0;
  }
  

Pro tip: Always limit your scanf input with %Ns (where N is one less than your buffer size) to prevent buffer overflow—this is a super common source of bugs.

2. How to Check if Runtime Errors Are From Your Operations #

Runtime errors in C almost always tie back to memory issues or incorrect input/output handling. Here's how to diagnose:

• Turn on compiler warnings: Compile your code with flags like -Wall -Wextra (if using GCC/Clang). These warnings will point out things like uninitialized pointers, type mismatches, or missing return values—stuff that often causes crashes later.
• Check for memory mistakes: Did you forget to allocate memory for pointers? Are you writing past the end of an array? These are the #1 causes of runtime crashes.
• Verify input/output formats: Make sure your scanf format specifiers match the variable types. For example, using %s for an int variable will mess things up big time.
• Use a debugger: Tools like gdb can help you step through your code line by line and see exactly where it crashes. Just compile with -g (to add debug info), then run gdb ./your-program and use commands like run, backtrace to find the issue.

If you can share a snippet of your code, it'd be even easier to pinpoint the exact problem—but even without it, following these steps should help you track down most issues.

内容的提问来源于stack exchange，提问作者Minhaj Ansari