×
INDI Library v1.8.5 Released (19 Apr 2020)

April 2020 release of INDI Library v1.8.5 introduces new drivers while providing fixes and improvements to existing devices and core framework.

stack smashing trackdown

6 months 4 weeks ago
sterne-jaeger
Platinum Boarder
Platinum Boarder
Posts: 599
Karma: 6
More
Topic Author
stack smashing trackdown #48012
Hi,
my newly developed INDI driver is functionally fine, but having it running an entire day shows this error:
2020-01-14T10:00:11: Driver indi_weatherradio: *** stack smashing detected ***: <unknown> terminated
2020-01-14T10:00:11: Driver indi_weatherradio: stderr EOF
<delProperty device="Weather Radio"/>
2020-01-14T10:00:11: Driver indi_weatherradio: restart #1
Child process 1650 died

Any hints how to track this down?

Wolfgang

TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | Moravian G2-8300 + ASI 1600mm pro + ASI 294mc pro | KStars/INDI on Raspberry Pi 4 with Raspbian 10

Please Log in or Create an account to join the conversation.

6 months 4 weeks ago
jpaana
Gold Boarder
Gold Boarder
Posts: 262
Karma: 5
More
stack smashing trackdown #48015
That's error from compiler inserted bounds checking that you are usually writing past some locally declared array from either end. Running under gdb should show roughly where on function level as it's only run when returning from a function, so running with valgrind for example might show it earlier as it checks each access. Defining -D_FORTIFY_SOURCE=2 to compile flags might show it earlier too, but I think it's already the default on most distributions.

Remote observatory running Ubuntu 20.04 x64 with ScopeDome 2M, Skywatcher EQ8, TS 8" RC, Atik 383L+, ASI178MC, ASI120MM-S, SX Lodestar X2, SX USB wheel with OAG, ZWO EAF, Gemini SnapCap, USB_DewPoint, KomaHub
The following user(s) said Thank You sterne-jaeger

Please Log in or Create an account to join the conversation.

6 months 4 weeks ago
sterne-jaeger
Platinum Boarder
Platinum Boarder
Posts: 599
Karma: 6
More
Topic Author
stack smashing trackdown #48027
Indeed, -D_FORTIFY_SOURCE=2 is set for Indi-3rdparty. I think I found the place where the memory violation is created.

Is there an option to catch this exception?

- Wolfgang

TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | Moravian G2-8300 + ASI 1600mm pro + ASI 294mc pro | KStars/INDI on Raspberry Pi 4 with Raspbian 10

Please Log in or Create an account to join the conversation.

Time to create page: 0.270 seconds