Skip to content

Would like a tool to do symbolication (ideally, would like "flutter logs"/"flutter run" to do it automatically) #16765

Open

Description

@eseidelGoogle

Related to #1016

Would be really nice to have a tool to symbolicate, e.g. follow the steps of:
https://github.com/flutter/engine/wiki/Symbolicating-production-crash-stacks

Including from custom engine builds. We hit an issue recently with customer:gold where they are building their own engine with cherry-picks, thus our normal symbolication instructions break down. Would be nice if we could point them to a script to symbolicate.

Activity

  1. changed the title [-]Would like a tool to do symbolication[/-] [+]Would like a tool to do symbolication (ideally, would like "flutter logs"/"flutter run" to do it automatically)[/+] on Apr 19, 2018
  2. Hixie commented on Apr 19, 2018

    @Hixie
    Contributor

    Ideally, "flutter logs"/"flutter run" would do it automatically.

  3. eseidelGoogle commented on Apr 20, 2018

    @eseidelGoogle
    ContributorAuthor

    @Hixie I believe #1016 is about just that?

  4. eseidelGoogle commented on Apr 20, 2018

    @eseidelGoogle
    ContributorAuthor

    This was more for capturing the case that customer:gold ran into where they had a custom built engine, but seeing that https://github.com/flutter/engine/wiki/Symbolicating-production-crash-stacks#symbolicating-local-builds is pretty simple as-is, maybe there is nothing to do there?

    I guess just the idea of separating out the "symbolicate this text" from "I happened to have seen it crash while flutter run was running" is what I was going for with this.

  5. Hixie commented on Apr 20, 2018

    @Hixie
    Contributor

    I don't think we really want to be encouraging people to build their own engines.

  6. added
    toolAffects the "flutter" command-line tool. See also t: labels.
    on Jul 20, 2018
  7. added this to the milestone on Jan 24, 2019
  8. added
    engineflutter/engine related. See also e: labels.
    on Jan 24, 2019
  9. added
    P2Important issues not at the top of the work list
    on May 29, 2020
  10. removed this from the milestone on Aug 17, 2020
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

    P2Important issues not at the top of the work listc: new featureNothing broken; request for a new capabilityengineflutter/engine related. See also e: labels.team-engineOwned by Engine teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-engineTriaged by Engine team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions