Skip to content

Android segfaults for API level <18 #9700

@sanxiyn

Description

@sanxiyn
Member

See #9120 for details. Probably related to how the logging system is initialized from the crate map using a weak symbol.

Activity

alexcrichton

alexcrichton commented on Oct 3, 2013

@alexcrichton
Member

I think that #9593 will start to hide the problem because it'll start handling when the symbol is NULL, but this is still a problem in that the reason it's NULL to begin with needs to be investigated.

sanxiyn

sanxiyn commented on Oct 5, 2013

@sanxiyn
MemberAuthor

I have posted a question to android-ndk regarding Android and weak symbol.

flaper87

flaper87 commented on Mar 10, 2014

@flaper87
Contributor

Triage bump. @alexcrichton @sanxiyn Do you know if this is still happening? Based on the gate, it doesn't look like but I don't have a good way to prove it.

@sanxiyn re weak symbols, some work started here #12556 by adding support for linkage flavors

alexcrichton

alexcrichton commented on Mar 10, 2014

@alexcrichton
Member

This does indeed appear to be working now, our android bot is definitely running tests with logging and crate maps. This has likely been fixed in the meantime.

Closing, but if this still reproduces, feel free to reopen!

added a commit that references this issue on Nov 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    I-crashIssue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.O-androidOperating system: Android

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @flaper87@sanxiyn@alexcrichton

        Issue actions

          Android segfaults for API level <18 · Issue #9700 · rust-lang/rust