Xcode运行C程序报错Thread 1:EXC_BAD_ACCESS，终端报Segmentation fault:11求助

Hey there! That Thread 1: EXC_BAD_ACCESS (and matching Segmentation fault: 11 in terminal) almost always points to invalid memory access—most likely tied to how your program handles the text file you’re working with, since you’ve already tried adjusting file locations. Let’s break down the most common fixes for this issue, especially with code from older textbooks like Programming in ANSI C:

1. Add Critical Error Checking for File Open Operations #

Older textbook code often skips error handling for fopen(), assuming the file will always be found. If the file isn’t in the right spot (or has a typo in its name), fopen() returns NULL—and trying to read/write from a NULL file pointer causes exactly the crash you’re seeing.

Update your code to include this check right after opening the file:

#include <stdio.h>
#include <stdlib.h> // For exit()

int main() {
    FILE *fp = fopen("your-file.txt", "r"); // Replace with your actual filename
    
    // Check if the file opened successfully
    if (fp == NULL) {
        perror("Error opening file"); // Prints a human-readable error (e.g., "No such file or directory")
        exit(EXIT_FAILURE); // Exit the program with an error code
    }
    
    // Rest of your program logic here...
    
    fclose(fp); // Don't forget to close the file when done!
    return 0;
}

This will tell you exactly why the file isn’t opening instead of silently crashing.

2. Confirm Your Program’s Working Directory #

Xcode runs your program from a hidden DerivedData folder, not the folder where your source code lives—so even if you put the text file next to your .c file, the program can’t find it.

To see where your program is actually running, add this code to print the current working directory:

#include <unistd.h> // For getcwd()

// Inside main(), before opening the file:
char current_dir[1024];
if (getcwd(current_dir, sizeof(current_dir)) != NULL) {
    printf("Program running from: %s\n", current_dir);
} else {
    perror("Failed to get working directory");
}

Run the program, copy the printed path, and move your text file into that folder. Alternatively, use an absolute path to the file in fopen() (e.g., fopen("/Users/your-username/Documents/your-file.txt", "r")).

For terminal runs: Make sure you’re in the same directory as the text file when you execute the program, or use the full path to the file.

3. Check for Other Invalid Memory Operations #

If the file check doesn’t fix the crash, look for other common bugs in the textbook code:

• Uninitialized pointers (e.g., using a char* that hasn’t been allocated memory with malloc())
• Array index out-of-bounds (e.g., accessing array[10] when the array only has 10 elements, indexes 0-9)
• Missing & in scanf() for non-pointer variables (e.g., scanf("%d", num) instead of scanf("%d", &num))

Quick Test #

First, run the updated code with the file open error check. If it prints an error about the file not being found, you know the issue is just the file location. If it still crashes, the problem is likely a pointer or memory access bug elsewhere in the code—share the specific snippet if you need help narrowing that down!

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