Segmentation 11 in own stack implementation in C

Question

Im trying to implement my own stack program, but when I initialize the stack I get the SEGMENTATION FAULT!

extern int stackInit(intstack_t* self){
self = malloc(sizeof(intstack_t));
if(self == NULL){
    fprintf(stderr,"Out of memory.");
    free(self);
    exit(-1);
}

self->bottom = malloc(MINIMUM_SIZE * sizeof(int));
if(self->bottom == NULL){
    fprintf(stderr,"Out of memory.");
    free(self->bottom);
    exit(-1);
}
self->top = self->bottom - 1;
self->allocated_top = self->bottom + MINIMUM_SIZE -1;
return 0;
}

int main()
{
intstack_t stack;

stackInit(&stack);
stackPush(&stack, 1);
stackPush(&stack, 2);
stackPush(&stack, 3);
}

extern void stackPush(intstack_t* self, int i){

//check if the stack is full and double its size if so.
if(self->top == self->allocated_top){
    ptrdiff_t total = self->top - self->bottom +1;
    ptrdiff_t new_total = GROWTH_FACTOR + total;
    self->bottom = realloc(self->bottom, new_total * sizeof(int));
    if(self->bottom == NULL){
        fprintf(stderr,"Out of memory.");
        free(self->bottom);
        exit(-1);
    }
    self->top = self->bottom + total - 1;
    self->allocated_top = self->bottom + new_total - 1;
}
*(++self->top) = i;
}

and here is the struct:

typedef struct
{
int* bottom;
int* top;
int* allocated_top;

} intstack_t;

and when I compile it with valgrind I get this: Use of uninitialised value of size 8 ==2744731== at 0x4008B2: stackPush (in /vol/fob-vol2/mi16/sajoseig/Compilerbau/lab1/stack) ==2744731== by 0x4009AB: main (in /vol/fob-vol2/mi16/sajoseig/Compilerbau/lab1/stack) ==2744731== Uninitialised value was created by a stack allocation ==2744731== at 0x400987: main (in /vol/fob-vol2/mi16/sajoseig/Compilerbau/lab1/stack)

==2744731== Conditional jump or move depends on uninitialised value(s) ==2744731== at 0x4007C5: stackPush (in /vol/fob-vol2/mi16/sajoseig/Compilerbau/lab1/stack) ==2744731== by 0x4009AB: main (in /vol/fob-vol2/mi16/sajoseig/Compilerbau/lab1/stack) ==2744731== Uninitialised value was created by a stack allocation ==2744731== at 0x400987: main (in /vol/fob-vol2/mi16/sajoseig/Compilerbau/lab1/stack)

==2744731== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==2744731== Bad permissions for mapped region at address 0x4005F4 ==2744731== at 0x4008B2: stackPush (in /vol/fob-vol2/mi16/sajoseig/Compilerbau/lab1/stack) ==2744731== by 0x4009AB: main (in /vol/fob-vol2/mi16/sajoseig/Compilerbau/lab1/stack)

If self is NULL you can't free it, the same with the self->bottom. — anastaciu
– anastaciu, Commented May 16, 2020 at 14:58
@anastaciu whoops sorry misread your comment. You are correct! — lurker
– lurker, Commented May 16, 2020 at 15:04

Cristian Bidea · Accepted Answer · 2020-05-16 15:09:06Z

2

The problem stems from the fact that you declared the init function to take an intstack_t * but that pointer is copied. So basically the address of the local variable stack is copied into a local variable and then overwritten locally by the assignment of the returned address of malloc, so the stack variable remains unchanged (uninitialized).

A solution is to modify the function to use a double pointer:

extern int stackInit(intstack_t **self) {
// instead of self you write (*self)
}

or a reference to pointer.

extern int stackInit(intstack_t *&self) {
// the function remain unchanged
}

But you have to make sure that you're actually using a pointer!

intstack_t *stack;

stackInit(&stack); // for the reference version stackInit(stack) should be called
stackPush(stack, 1);
stackPush(stack, 2);
stackPush(stack, 3);

answered May 16, 2020 at 15:09

Cristian Bidea

7094 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Nacho Sanjose Over a year ago

Thanks for the tips! it was indeed that the pointer was copied, I just had to delete that malloc() line!

Collectives™ on Stack Overflow

Segmentation 11 in own stack implementation in C

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related