Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Add an ASan build#848

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Draft
geofft wants to merge2 commits intomain
base:main
Choose a base branch
Loading
fromgeofft/asan
Draft

Add an ASan build#848

geofft wants to merge2 commits intomainfromgeofft/asan

Conversation

@geofft
Copy link
Collaborator

No description provided.

@geofft
Copy link
CollaboratorAuthor

This is very badly implemented, I just want to see how far it gets with this much effort.

@jjhelmus
Copy link
Contributor

Would adebug+asan configuration make more sense thenpgo+lto+asan? Is there many cases where you want to find memory issues in an optimized build?

@jjhelmus
Copy link
Contributor

Interesting. ncurses looks to have a memory leak that is triggered when running tic

2025-11-06T20:20:19.4276994Z ncurses> 1833 entries written to /build/out/usr/share/terminfo2025-11-06T20:20:19.5434638Z ncurses> =================================================================2025-11-06T20:20:19.5438853Z ncurses> ==6084==ERROR: LeakSanitizer: detected memory leaks2025-11-06T20:20:19.5439440Z ncurses> 2025-11-06T20:20:19.5439788Z ncurses> Direct leak of 1066464 byte(s) in 322 object(s) allocated from:2025-11-06T20:20:19.5442104Z ncurses>     #0 0x5616aae2b5f4 in malloc /build/llvm/compiler-rt/lib/asan/asan_malloc_linux.cpp:67:32025-11-06T20:20:19.5443653Z ncurses>     #1 0x5616aaeba30d in _nc_init_termtype (/build/ncurses-6.5/progs/tic+0x19130d)2025-11-06T20:20:19.5447281Z ncurses>     #2 0x5616aaeee34c in _nc_init_entry (/build/ncurses-6.5/progs/tic+0x1c534c)2025-11-06T20:20:19.5452424Z ncurses>     #3 0x5616aaed2787 in _nc_parse_entry (/build/ncurses-6.5/progs/tic+0x1a9787)2025-11-06T20:20:19.5453104Z ncurses>     #4 0x5616aaecc56c in _nc_read_entry_source (/build/ncurses-6.5/progs/tic+0x1a356c)2025-11-06T20:20:19.5453624Z ncurses>     #5 0x5616aae6f6f2 in main (/build/ncurses-6.5/progs/tic+0x1466f2)2025-11-06T20:20:19.5454225Z ncurses>     #6 0x7f13fab43b44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44) (BuildId: 48c48bc6abb794461b8a558dd76b29876a0551f0)2025-11-06T20:20:19.5454723Z ncurses>

@geofft
Copy link
CollaboratorAuthor

Looks like this was previously reported inhttps://lists.gnu.org/archive/html/bug-ncurses/2024-11/msg00013.html and not really acted upon. I'm going to turn off leak detection in the build for now (and might turn off all sanitizers if this doesn't get far enough).

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

arch:x86_64libc:gnuplatform:linuxSpecific to the Linux platformpython:3.14

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@geofft@jjhelmus
[8]ページ先頭
©2009-2025 Movatter.jp