在Eclipse中进行C编程时的怪异行为

Q1. No, they are warnings as they are legit C code. It could be possible that you want such code. You can use -Werror on gcc to make warnings to errors. Also add some other flags for turning on more warnings like -Wall -Wpedantic -Wextra -Wshadow -Wconversion -Wno-sign-compare etc. This'd be a bit closer to what you're probably used to when using Java ;-)

Q2. Atleast on Linux you have coredumps, iirc Windows was minidumps. These can be loaded together with the corresponding executable into a debugger. Then you can access backtraces, values etc.

Q3.

Like above I asked about settings to make eclipse report the issue as fatal one or making crashes to generate report so that stuff can be fixed quickly instead of hours long debuggins.

Log yourself. Also there can be macros for easing this.

Do you use any better (and possibly involving smaller learning curve) alternative to (eclipse CDT + MinGW + Windows) that will provide more powerful debugging so that I can avoid such errors.

IDE is pretty irrelevant for C imho. Use Linux with native GCC instead, MinGW is nice but it can be daunting (my experience). Ofcourse MS VSC++ can also compile C but its just for C++ compatible thus not really specific to one standard.

Q4. Well, multiple errors occured which are listed. If it's difficult to reproduce it might be a problem in your setup, this is exactly the experience I had with MinGW on Windows.

Q5. It's the address -- you have a pointer to a pointer, so the first ("outer") pointer is that address, pointing to another pointer which is NULL. Or more verbosely: tempStructObj is a pointer to NULL (ie. an int_ptr which holds the value 0x0.

To function2 you pass another int_ptr which holds the semi-random value/address of the automatic variable int_ptr tempStructObj is stored Ie. you have such:

Address &tempStructObj: tempStructObj

in the RAM. When you then call function1, you pass the value of this (not-NULL) pointer. Of course the comparison is thus always false. You'd need to compare *param with NULL.

Even more: If you compile with GCC (on Linux) and use really verbose flags you get:

gcc -std=c99 -Wall -Wpedantic -Wextra -Wshadow -Wconversion -Wno-sign-compare -o main main.c
main.c: In function ‘function2’:
main.c:19:18: warning: passing argument 1 of ‘function1’ from incompatible pointer type [-Wincompatible-pointer-types]
     if(function1(param))
                  ^
main.c:12:5: note: expected ‘TempStruct * {aka struct TempStruct *}’ but argument is of type ‘TempStruct ** {aka struct TempStruct **}’
 int function1(TempStruct *param)
     ^

So exactly the problem you had ^^

另外，我将function1完全删除它，这完全没有必要，只是混淆了代码。另外，我会为struct和分别使用不同的名称，并在typedef后面附加一个_t。另外，我会将其移动到较短的代码段中。附带说明：\n在printf()-call中添加a 。

修改后的代码：

#include <stdio.h>
#include <limits.h>

typedef struct TempStruct_s {
    int a;
    struct TempStruct_s *next;
} TempStruct_t;

int function(TempStruct_t **param)
{
    if(!*param) {
        return INT_MIN;
    }
    *param = (*param)->next;
    return 0;
}

int main()
{
    TempStruct_t *tempStructObj = NULL;
    function(&tempStructObj);
    printf("Does not reach here!!!\n");
    return 0;
}