native: compile with -g, "make term" runs through gdb

[kaspar030]

Trying to debug #5040...

[kaspar030]

Let's see if this shows a backtrace in Murdock ...

[cgundogan]

I am full of excitement

[cgundogan]

Terminal program gdb -ex r -ex bt -batch /data/riotbuild/tests/unittests/bin/native/unittests.elf not found. Aborting.

[kaspar030]

No gdb in the riot docker images?

[cgundogan]

No gdb in the riot docker images?

ah yes, I had to install gdb manually yesterday, too when I was testing out docker

[kaspar030]

I'll add it to the murdock image...

[OlegHahm]

Program received signal SIGSEGV, Segmentation fault.
0x0804baaf in main () at main.c:40
40 while(1) *fail++ = '\0';
#0 0x0804baaf in main () at main.c:40

looks "good" 👍

[kaspar030]

Ok, I'll drop the fail commit.

[cgundogan]

hmm .. not sure if we should opt for running gdb as TERMPROG default.. Isn't this why we have the targets all-debug and debug on native?

[kaspar030]

Hm. I see your point.
Does it hurt?

[kaspar030]

"all-debug" builds with debug symbols, so indeed, that would be redundant.
"debug" starts a full debugging session. This PR uses gdb's "-batch" mode, which is exactly for the purpose of getting backtraces, without launching a full interactive session.

IMHO, for native, performance didn't really matter in the past (as we're building without any optimization), and so always adding the debug symbols will probably make life easier for us devs.

[cgundogan]

well .. for now this will break our riot docker image, because we have no gdb installed there by default. I agree with you that this will not hurt anything on native, so I will probably ACK because of the usefulness that we win from this. An alternative would be to use the gdb command in the test scripts instead of using make term/test What do you think about that?

[kaspar030]

An alternative would be to use the gdb command in the test scripts instead of using make term/test What do you think about that?

Yes, or better, just set the term line for our static tests. I'll update.

[cgundogan]

Yes, or better, just set the term line for our static tests. I'll update.

ah right 👍

[kaspar030]

Works perfectly. Should we merge, so we can see what's wrong in #5040? ;)

[OlegHahm]

Let's go!

[kaspar030]

dockerfile PR: RIOT-OS/riotdocker#20

[Yonezawa-T2]

I got the following message from Travis:

 Terminal program gdb -batch -ex r -ex bt /home/travis/build/RIOT-OS/RIOT/tests/unittests/bin/native/unittests.elf not found. Aborting.

https://travis-ci.org/RIOT-OS/RIOT/jobs/118144712

The message is also generated from CI of this PR.
https://travis-ci.org/RIOT-OS/RIOT/jobs/118095472

Is the message relate to this PR? Is Travis deprecated in favor of RIOT CI?