1 Reply by piotrp

(12 replies, posted in wolfSSL)

Hello All!

-g1 is the same as -ggdb1 in case of my gcc version.
It does not allow to debug the ssl code.

I'm working in embedded environment where I have no well known OS, because of that I have to check what is not working in it.

Thanks in advnace!
Piotr P.

Go to forum: wolfSSL

2 Reply by piotrp

(12 replies, posted in wolfSSL)

Hello all!

Unfortunately suggested solution does not work everywhere.
I'm using gcc 4.7.2 for embedded devices.
I've added following flags to cflags: -ggdb -feliminate-unused-debug-symbols -fdebug-types-section
and it ends with ld.exe: final link failed: Memory exhausted.

What more I've checked it with gcc 4.9.3 and result was exactly the same.

When use -ggdb1 it passes link stage but debugging is not possible.

Is there any solution to the problem?
Any ideas about cause of the problem?

The library is quite small, so it should not end with memory problems during linkage.

Best regards,
Piotr P.

Go to forum: wolfSSL