Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Program received signal SIGABRT, Aborted

There is a structure in my program

struct List      
{
    int data;
    List *next;
};

and a function of adding an element to the tail of the list:

void addL(List* &tail, int dat)   
{

    if (tail==NULL) 
    {
        tail = new List;
        tail->data = dat; 
        tail->next=NULL;
    }   
    else
    {
        tail->next = new List;
        tail = tail->next;
        tail->data = dat;
        tail->next = NULL;
    }
}

gdb says about the problem

terminate called after throwing an instance of 'St9bad_alloc'
  what():  std::bad_alloc

Program received signal SIGABRT, Aborted.
0xb7fdd424 in __kernel_vsyscall ()

in line

tail->next = new List;

I tried to make another variable of type List like that:

List* add;
add = new List;

but got the same problem in second line.

How to rewrite this correctly? And is it any need to paste here the function which calls addL? Sorry, if this question had already been asked, I could not understand while looking through them.

like image 367
Tami Avatar asked Apr 05 '15 17:04

Tami


People also ask

What is SIGABRT abort?

The SIGABRT only indicates that the app called abort() — that is, crashed deliberately. This can happen as a result of an error unwrapping a Swift optional (which can be an unconnected outlet), but there are plenty of other possibilities).

What is a SIGABRT signal?

The SIGABRT signal is raised when the abort function is called or when a user ABEND occurs. SIGABRT may not be raised for an ABEND issued by the SAS/C library, depending on the severity of the problem. Default handling. By default, SIGABRT causes abnormal program termination.

What causes SIGABRT error?

A SIGABRT is caused if your program aborted due to a fatal error. This can also be caused if you are using an assert() which fails or an abort(). Fix : In C++, this is normally due to an assert statement in C++ not returning true, but some STL elements can generate this if they try to store too much memory.


1 Answers

Either you are out of memory (maybe your list is too big for your memory) or you are trying somewhere in the memory that you are not allowed to.


Since the list is small, then I suspect this is the issue (as stated here):

abort() is usually called by library functions which detect an internal error or some seriously broken constraint. For example malloc() will call abort() if its internal structures are damaged by a heap overflow.

Another relevant question lies here.

So I suggest you take a piece of paper and a pen and draw what your code does. There is probably a tangling pointer or something.

like image 200
gsamaras Avatar answered Sep 18 '22 03:09

gsamaras