Summary: | decode_linespec_1 vagrind errors on "" | ||
---|---|---|---|
Product: | gdb | Reporter: | Jan Kratochvil <jan> |
Component: | symtab | Assignee: | Tom Tromey <tromey> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | keiths, tromey |
Priority: | P2 | ||
Version: | HEAD | ||
Target Milestone: | 10.1 | ||
Host: | x86_64-fedora15-linux-gnu | Target: | x86_64-fedora15-linux-gnu |
Build: | Last reconfirmed: |
Description
Jan Kratochvil
2011-03-02 20:43:46 UTC
Sending a patch. The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ff47f4f06d296b672337e2c7363a745cd2725f58 commit ff47f4f06d296b672337e2c7363a745cd2725f58 Author: Tom Tromey <tom@tromey.com> Date: Sat Dec 21 09:51:05 2019 -0700 Fix valgrind error from gdb.decode_line PR symtab/12535 points out that gdb.decode_line("") will cause a valgrind report. I think the empty linespec does not really make sense. So, this patch changes gdb.decode_line to treat a whitespace-only linespec the same as a non-existing argument. gdb/ChangeLog 2020-01-14 Tom Tromey <tom@tromey.com> PR symtab/12535: * python/python.c (gdbpy_decode_line): Treat empty string the same as no argument. gdb/testsuite/ChangeLog 2020-01-14 Tom Tromey <tom@tromey.com> PR symtab/12535: * gdb.python/python.exp: Test decode_line with empty string argument. Change-Id: I1d95812b4b7a21d69a3e9afd05b9e3141a931897 Fixed. |