From: Michal Ludvig <mludvig@suse.cz>
To: GDB Patches <gdb-patches@sources.redhat.com>
Subject: [RFA] Avoid segfault in decode_line_2
Date: Fri, 11 Jul 2003 07:06:00 -0000 [thread overview]
Message-ID: <3F0E61E7.5020900@suse.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
Hi all,
this patch fixes a problem that I met while debugging a testsuite
failure on amd64:
> Running gdb-head/gdb/testsuite/gdb.c++/templates.exp ...
> FAIL: gdb.c++/templates.exp: constructor breakpoint (timeout)
(gdb) break T5<int>::T5
-> Segfault in linespec.c:486 [decode_line_2()] because
values.sals[i].symtab is NULL and dereferencing of
values.sals[i].symtab->filename crashes.
After some investigation I found out that .debug_line section of the
input file was broken (reported to binutils@ list).
However broken debug info is not an excuse for GDB to crash.
OK to apply to head and branch?
Michal Ludvig
--
* SuSE CR, s.r.o * mludvig@suse.cz
* (+420) 296.545.373 * http://www.suse.cz
[-- Attachment #2: linespec-safety-1.diff --]
[-- Type: text/plain, Size: 1123 bytes --]
2003-07-11 Michal Ludvig <mludvig@suse.cz>
* linespec.c (decode_line_2): Avoid crash if
find_function_start_sal() returns empty record.
Index: linespec.c
===================================================================
RCS file: /cvs/src/src/gdb/linespec.c,v
retrieving revision 1.49
diff -u -p -r1.49 linespec.c
--- linespec.c 8 Jun 2003 18:27:13 -0000 1.49
+++ linespec.c 11 Jul 2003 06:59:01 -0000
@@ -483,11 +483,16 @@ decode_line_2 (struct symbol *sym_arr[],
if (sym_arr[i] && SYMBOL_CLASS (sym_arr[i]) == LOC_BLOCK)
{
values.sals[i] = find_function_start_sal (sym_arr[i], funfirstline);
- printf_unfiltered ("[%d] %s at %s:%d\n",
+ printf_unfiltered ("[%d] %s at %s:%d ",
(i + 2),
SYMBOL_PRINT_NAME (sym_arr[i]),
- values.sals[i].symtab->filename,
+ values.sals[i].symtab ?
+ values.sals[i].symtab->filename :
+ "?FILE",
values.sals[i].line);
+ if (! values.sals[i].symtab)
+ printf_unfiltered ("[No symtab? Probably a broken debug info...]" );
+ printf_unfiltered ("\n");
}
else
printf_unfiltered ("?HERE\n");
next reply other threads:[~2003-07-11 7:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 7:06 Michal Ludvig [this message]
2003-07-18 13:18 ` Elena Zannoni
2003-07-23 19:38 ` Elena Zannoni
2003-07-24 6:27 ` Michal Ludvig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F0E61E7.5020900@suse.cz \
--to=mludvig@suse.cz \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox