Bug 470830 - Don't print actions vgdb me ... continue for vgdb --multi mode
Summary: Don't print actions vgdb me ... continue for vgdb --multi mode
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (other bugs)
Version First Reported In: 3.21.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-09 13:26 UTC by Mark Wielaard
Modified: 2023-06-15 15:50 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Don't print action vgdb me and continuing in vgdb --multi mode (4.34 KB, text/plain)
2023-06-09 13:26 UTC, Mark Wielaard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Wielaard 2023-06-09 13:26:45 UTC
Created attachment 159565 [details]
Don't print action vgdb me and continuing in vgdb --multi mode

When in vgdb --multi mode we know gdb is already attached and most likely running inside gdb already. So it doesn't really add much information to print "(action) vgdb me ..." and "Continuing ..." before/after each gdb prompt.

Guard each printing with if (!(VG_(clo_launched_with_multi)))
Comment 1 Mark Wielaard 2023-06-15 15:50:15 UTC
commit bf0c73231b76e293a103ed8b2178975c7032f669
Author: Mark Wielaard <mark@klomp.org>
Date:   Fri Jun 9 15:21:57 2023 +0200

    Don't print action vgdb me ... and continuing ... in vgdb --multi mode
    
    Guard each (action) vgdb me ... VG_(umsg) printing with
      !(VG_(clo_launched_with_multi))
    
    https://bugs.kde.org/show_bug.cgi?id=470830