Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Internal] Stability Tracking Issue #122

Open
ProfFan opened this issue Sep 24, 2019 · 5 comments
Open

[Internal] Stability Tracking Issue #122

ProfFan opened this issue Sep 24, 2019 · 5 comments
Milestone

Comments

@ProfFan
Copy link
Collaborator

ProfFan commented Sep 24, 2019

This is a mega-thread used for improving GTSAM's stability.

Currently resolving bugs found by the LLVM sanitizer, a.k.a. hunting leaks and use-after-frees with Clang's ASAN.

@ProfFan
Copy link
Collaborator Author

ProfFan commented Sep 24, 2019

@ProfFan
Copy link
Collaborator Author

ProfFan commented Sep 24, 2019

Note that we should have two things for improving stability:

  • A fuzzer (afl or so) and a build machine that fuzz the library day after day
  • A mechanism for detection of hidden memory leaks, for example, make the TEST macros run in a loop that does the test 1000 times, and observe the memory footprint. Current test suite runs in ~20s, so 1000*20=20000s=6h is pretty reasonable.

@ProfFan ProfFan changed the title Tracking use-after-frees with Clang's ASAN [Internal] Stability Tracking Issue Sep 24, 2019
@dellaert
Copy link
Member

Yowza. Let's talk tomorrow.

@ProfFan
Copy link
Collaborator Author

ProfFan commented Sep 24, 2019

@dellaert Roger that

@ProfFan
Copy link
Collaborator Author

ProfFan commented Sep 24, 2019

Aiming to have AddressSanitizer and LeakSanitizer in Travis and in Tests.

#121

@ProfFan ProfFan added this to the GTSAM 4.1 milestone Sep 24, 2019
@dellaert dellaert modified the milestones: GTSAM 4.1, GTSAM 4.1.1 Jul 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants