Problem with disassembler and SIGILL signal

Amaury

@SGaist I am removing the translator because it looked like that was this function that send the SIGILL signal .
After all it seems that it doesn't changed anything, but I do need it , just that I can translate my pop-ups in a different way.

@mrjj I'm going to look those potential solutions and post here if I get the answer.

kshegunov

@Amaury
It'd be helpful if you also extract the assembly (a few lines) from the point of the crash, where you get the SIGILL.

Amaury

Those are the first 15 lines of the disassembler where I get my Sigill signal : it happens on line 6

0x6f6a2dd4                   00 00 00 00  andeq	r0, r0, r0
0x6f6a2dd8                   00 00 00 00  andeq	r0, r0, r0
0x6f6a2ddc                   00 00 00 00  andeq	r0, r0, r0
0x6f6a2de0                   fe e1 6e f2  vorr	q15, q15, q15
0x6f6a2de4                   1e ff 2f e1  bx	lr
0x6f6a2de8                   1d 0f 19 ee  mrc	15, 0, r0, cr9, cr13, {0}
0x6f6a2dec                   1e ff 2f e1  bx	lr
0x6f6a2df0                   9f 2f 90 e1  ldrex	r2, [r0]
0x6f6a2df4                   01 30 82 e0  add	r3, r2, r1
0x6f6a2df8                   93 2f 80 e1  strex	r2, r3, [r0]
0x6f6a2dfc                   00 00 52 e3  cmp	r2, #0
0x6f6a2e00                   fa ff ff 1a  bne	0x6f6a2df0
0x6f6a2e04                   03 00 a0 e1  mov	r0, r3
0x6f6a2e08                   1e ff 2f e1  bx	lr
        Function: OPENSSL_cleanse

Amaury

Hi there ,

after a day of research I finnaly didn't found what's the real problem .

I read that the return a.exec() Will execute only when a signal is send to it ( when nothing is shown).

I maybe found a track that leads to my destructors , I have some sql request and QUrl posts in my program , ido I need to delete them in the destructor , would that cause a problem if the program is executed during a long time ?

Everything is compiling fine and my program is running well but after a period of time it's crashing.

Finally I was thinking about the SIGILL signal ,when I F10 or F11 on this it's running this part of the program but if it's closing everything on the app would it be normal to have this signal ?

don't know if I was clear ...

mrjj

Hi
SIGILL is not normal.
From normal program errors you do not get this in any easy way.
So the big question is. Can you can get SIGILL from a normal GUI program or
only when using your full code?

It might be some sort of corruption but impossible to guess at :)

Amaury

I didn't tried that but it works with another program I don't have any SIGILL error ...

the problem with this is that I have something like 18 pages and 500 lines by pages on average.

So that said to find out where the problem is do I have to check each lines of my program ? :/

mrjj

@Amaury
Well if ONLY this program does it. Its not compiler.
But you should be really clear about it.
Else you can waste tons of time.

So yes, if it is program error in your code. You will need to find the actual line/the bug.

You can try http://valgrind.org/ but its takes time to use and understand.

Amaury

Thanks for the support , I need to debug my program before I continue so I prefer to waste little time to understand and use the program.
I can't try to debug the code line per line it would take too long and it should be everywhere .

At least when I'm done with it I finally have to find a solution to start my app on boot but for now if it crashes all the time it's not really usefull.

mrjj

@Amaury
Well u should look for array copy. dangling pointers.
old char * types and stuff like that.
To get SIGILL from program bug , you must corrupt
something in the code segment.
Easy way is to use dangling pointer.

So maybe you can guess at functions where it might happen.

Amaury

@mrjj
Well right now you're talking to me in japanese ^^
I'm going to have a look on that didn't had time yesterday , I think I can be helped for one thing or two :)
I'll come back if my problem is solve or not.

mrjj

@Amaury

Oh :) sorry.
What i mean is SIGILL means "what the hell is that instruction" from the cpu.
This can happen if compiler setting is slightly off for target.
OR
you can also have it happen if you write over the end of an array
or use a pointer that is not set.
Like
MyClass *c1; /// dangling pointer
c1->somfunc()
Then when CPU tries to run the func it sees some random garbage at that location
and might say SIGILL.

Amaury

Alright that's clearer ^^
So if I need to create a dangling pointer where do I need to declare it ?
into the class itself ?

mrjj

@Amaury
Well you can declare it anywhere. :)
You want to try crash on purpose`?

Amaury

Yes I'd like to look at all my pointers, see if there's somewhere that one is not declared or thing like that.

mrjj

@Amaury

one is not declared
I assume you mean instantiated or in non japanese
new'ed
as in
ClassX * varX = new X()

Amaury

Yes that's alright .

Btw I got a question , there's some code that I didn't develop myself and I was wondering if there could be an error in some parameters here's the setup :

main.cpp


static const QString path = "localhost";
DataBase MemTampon::Db(path);

int main(int argc, char *argv[])
{
    QApplication a(argc, argv);

    QTextCodec::setCodecForCStrings(QTextCodec::codecForName("UTF-8"));
    QTextCodec::setCodecForTr(QTextCodec::codecForName("UTF-8"));

    QTranslator *qtTranslator = new QTranslator;
        qtTranslator->load("qt_" + QLocale::system().name(), QLibraryInfo::location(QLibraryInfo::TranslationsPath));
        a.installTranslator(qtTranslator);

        MemTampon::Db.aff_Temperature();
        MemTampon::Db.aff_Humidite();
        MemTampon::Db.aff_Puissance();
        MemTampon::Db.aff_Nom_SD();

    MainWindow w;
    w.show();

    return a.exec();

}

memtampon.h (memtampon.cpp is empty)

class MemTampon
{
public:
    static DataBase Db;
    static Options Opt;

};

and Database.cpp

DataBase::DataBase(const QString &path)
{
        db = QSqlDatabase::addDatabase("QMYSQL");
        db.setHostName("localhost");
        db.setDatabaseName("SmartDevice_DB_V1");
        db.setUserName("root");
        db.setPassword("root");

        if (!db.open())
        {
           qDebug() << "Error: connection with database fail";
        }
        else
        {
           qDebug() << "Database: connection ok";
        }
}

I assume that with the path variable I am able to call the functions that are in my cpp but, it tells me that path is an unused parameter could it possibly give me an error ?

mrjj

Its impossible to say
But global variables are good candidate to be check. (always)

I dont think
static const QString path;
can give such error.

Amaury

Thank you I was a little disapointed by this function and wasn't able to say if that was correct or not

mrjj

@Amaury
Well you can always single step it and see if something happens.

kshegunov

@Amaury
Also you can cut the code that you suspect and see if the problem manifest itself. I wouldn't in principle initialize anything outside of main (like your database) if I can help it, that way I stumble on to less errors in my code, and thus makes for an easier time debugging. Still, my best guess is there some subtle architecture mismatch, so the compiler generates a mostly valid code. However I have no clue how to really test that at present.