Revision history [back]

Thanks for the hints. Here are some follow-ups.

I added launch-prefix="xterm -e gdb --args" in the launch file, and when the node finally crashes, here is the information in gdb window: ... [Thread 0xb21ffb70 (LWP 5438) exited] [Thread 0xb2be0b70 (LWP 5437) exited] [Thread 0xb3be2b70 (LWP 5435) exited] [Thread 0xb33e1b70 (LWP 5436) exited] Program exited with code 050 (gdb) bt No stack ...

As regards memory leakage, there is no obvious increase of memory usage throughout the running inside system monitor.

Any further advice?

Thanks for the hints. Here are some follow-ups.

I added launch-prefix="xterm -e gdb --args" in the launch file, and when the node finally crashes, here is the information in gdb window: ... [Thread 0xb21ffb70 (LWP 5438) exited] [Thread 0xb2be0b70 (LWP 5437) exited] exited]

[Thread 0xb3be2b70 (LWP 5435) exited] exited]

[Thread 0xb33e1b70 (LWP 5436) exited] exited]

Program exited with code 050 (gdb) bt No stack ...

As regards memory leakage, there is no obvious increase of memory usage throughout the running inside system monitor.

Any further advice?

Thanks for the hints. Here are some follow-ups.

I added launch-prefix="xterm -e gdb --args" in the launch file, and when the node finally crashes, here is the information in gdb window: ... window:

...

[Thread 0xb21ffb70 (LWP 5438) exited] exited]

[Thread 0xb2be0b70 (LWP 5437) exited]

[Thread 0xb3be2b70 (LWP 5435) exited]

[Thread 0xb33e1b70 (LWP 5436) exited]

Program exited with code 050 050

(gdb) bt bt

No stack stack

...

As regards memory leakage, there is no obvious increase of memory usage throughout the running inside system monitor.

Any further advice?