This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/1336: -Wformat-nonliteral vs valprint.c - use format methods?
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 16 Aug 2003 18:02:01 -0000
- Subject: gdb/1336: -Wformat-nonliteral vs valprint.c - use format methods?
- Reply-to: ac131313 at redhat dot com
>Number: 1336
>Category: gdb
>Synopsis: -Wformat-nonliteral vs valprint.c - use format methods?
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: maintenance
>Submitter-Id: net
>Arrival-Date: Sat Aug 16 18:08:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
valprint.c doesn't get on well with -Wformat-nonliteral. The problem is comming from the language vector returning full or partial format strings and then using them as printf format parameters.
This will take something of an overhaul to fix. I guess, instead of the format strings, LONGEST / DOUBLEST stringify methods could be used. Something along the lines of paddr() et.al.?
Note that there is also a PR to add a format / print address method.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: