| Summary: | Don't print actions vgdb me ... continue for vgdb --multi mode | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Mark Wielaard <mark> |
| Component: | general | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ahajkova, philippe.waroquiers, pjfloyd |
| Priority: | NOR | ||
| Version First Reported In: | 3.21.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Don't print action vgdb me and continuing in vgdb --multi mode | ||
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 |
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)))