-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Closed
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work liste: engine-toolEngine-specific tooling (i.e. `tools/engine_tool`).Engine-specific tooling (i.e. `tools/engine_tool`).team-engineOwned by Engine teamOwned by Engine teamtriaged-engineTriaged by Engine teamTriaged by Engine team
Description
The paths in the debug symbols for et builds are not valid which makes debugging them difficult. I don't know of a workaround yet.
platform: macos
type: cppdbg
MIMode: lldb
steps to reproduce
- build
impeller_unittestswithet - in vscode set a symbolic breakpoint
- execute
impeller_unittestsin the vscode debugger - when the breakpoint is hit, notice that the stacktrace has the correct symbols, but clicking on the stack frames does not jump to the proper file. The path is something like
b/f/w/flutter/impeller/aiks/canvas.cc, not a valid path.
screenshot
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work liste: engine-toolEngine-specific tooling (i.e. `tools/engine_tool`).Engine-specific tooling (i.e. `tools/engine_tool`).team-engineOwned by Engine teamOwned by Engine teamtriaged-engineTriaged by Engine teamTriaged by Engine team