Skip to content

Include Some Indication of Which File / Analysis an Error Belongs To In a Project #7821

Open
Enhancement
Open
Include Some Indication of Which File / Analysis an Error Belongs To In a Project#7821
Enhancement
Labels
UI: LogsIssues with the Log area

Description

@utkonos
utkonos
opened on Dec 22, 2025

What is the feature you'd like to have?
If you open more than one file at the same time to get them all simultaneously processing from a project, and one has an important failure that you may want to look more carefully at, please include somewhere in the error information that will help the user figure out which file it was that caused the error.

Is your feature request related to a problem?
I am seeing one or two Itanium RTTI failures when opening a set of files from a project. And I can't easily tell which file caused the error without closing them all and then opening them one by one to isolate the problem.

Additional Information:

Image

Activity

  1. emesare commented on Dec 22, 2025

    @emesare
    emesare
    on Dec 22, 2025
    Member

    There is three things here really:

    1. Those logs should be scoped to the session (e.g. the binary associated with the log), but now that we scoped the logs to a session they disappear completely! (see 2)
    2. Session scoped logs are hidden by default when not in the tab (because you are analyzing in a project there is no tab for the binary) We need to determine how we want to show logs when analyzing multiple at a time within a project.
    3. If you display the session id in the log, it gives you a number, we need another display to show some friendly name for the binary. This would seem to entail some way of going from session id -> file metadata.
    Image

    Currently you can sidestep the issue of 2 by changing the log scope (right click in log panel and show all)

    Image

    1 is easy, and we are already in the process of fixing this issue for logs originating from rust code in this PR,

  2. emesare
    added the
    Enhancement
    issue type on Dec 22, 2025
  3. emesare
    added
    UI: LogsIssues with the Log area
    on Dec 22, 2025
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

    UI: LogsIssues with the Log area

    Type

    Enhancement

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions