Bug 388526

Summary: Inconsistent severity in message text: "WARNING: Serious error"
Product: [Developer tools] valgrind Reporter: Chug <chug>
Component: generalAssignee: Paul Floyd <pjfloyd>
Status: RESOLVED FIXED    
Severity: normal CC: pjfloyd
Priority: NOR    
Version First Reported In: 3.13.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Chug 2018-01-04 15:29:43 UTC 
As shown in https://bugs.kde.org/show_bug.cgi?id=387773

  --17775-- WARNING: Serious error when reading debug info

Is it a 'warning' or an 'error'? As an alternative consider:

  --17775-- WARNING: Failure reading debug info
Comment 1 Paul Floyd 2025-09-09 13:14:12 UTC 
In debuginfo.c

      VG_(message)(Vg_DebugMsg, "WARNING: Serious error when "
                                "reading debug info\n");
      if (True || VG_(clo_verbosity) < 2) {
         /* Need to show what the file name is, at verbosity levels 2
            or below, since that won't already have been shown */
         VG_(message)(Vg_DebugMsg, 
                      "When reading debug info from %s:\n",
                      (di && di->fsm.filename) ? di->fsm.filename
                                               : "???");
      }
      VG_(message)(Vg_DebugMsg, "%s\n", msg);

That does look like a bit of a mess.

The "if (True ||" bit can be cleaned up.
The two lines that always get printed are

WARNING: Serious error when reading debug info
When reading debug info from [filename]

I suggest changing that to
WARNING: Serious problem reading debug info from [filename]/
WARNING: Valgrind will continue to execute but error messages may be degraded.
Comment 2 Paul Floyd 2025-09-09 19:07:37 UTC 
commit a2b8fcbad704523be08744356e8cae8b9867828c (HEAD -> master, origin/master, origin/HEAD)
Author: Paul Floyd <pjfloyd@wanadoo.fr>
Date:   Tue Sep 9 21:05:37 2025 +0200

    Bug 388526 -Inconsistent severity in message text: "WARNING: Serious error"