From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] remote.c: Avoid multiple serial_close calls on baud rate error
Date: Fri, 05 Dec 2003 20:36:00 -0000 [thread overview]
Message-ID: <1031205203631.ZM15513@localhost.localdomain> (raw)
One of my colleagues recently noticed the following:
(gdb) set remotebaud 0x100000
(gdb) target remote /dev/ttyS0
warning: Invalid baud rate 1048576. Maximum value is 460800.
/dev/ttyS0: Invalid argument.
(gdb) set remotebaud 230400
(gdb) target remote /dev/ttyS0
Segmentation fault
The reason for this SEGV is that remote.c was closing ``remote_desc''
twice. On the second attempted close, it was accessing some data
structures through some already freed (and probably even reallocated)
memory.
The comment that I've added explains how the double close is avoided.
FWIW, I considered calling remote_close(), but decided against it
since remote_desc can not be passed explicitly to this function.
Also, if the implementation of remote_close() were to change in some
way, it may end up doing more (or less) than what's desired for
handling the baud rate error. Conversely, a hypothetical change in
remote_close() may require that the error handling code be changed in
a similar fashion, so the preferred path to fixing this problem isn't
quite so clear cut. Therefore, I'm willing to revise this patch to
call remote_close() instead if that's deemed preferable.
With regard to the testcase above, it'd be nice if this could be added
to the testsuite, but I can't think of a portable way of doing so.
Okay?
* remote.c (remote_open_1, remote_cisco_open): Avoid closing
remote_desc more than once.
Index: remote.c
===================================================================
RCS file: /cvs/src/src/gdb/remote.c,v
retrieving revision 1.122
diff -u -p -r1.122 remote.c
--- remote.c 10 Nov 2003 21:20:44 -0000 1.122
+++ remote.c 5 Dec 2003 19:58:17 -0000
@@ -2299,7 +2299,12 @@ remote_open_1 (char *name, int from_tty,
{
if (serial_setbaudrate (remote_desc, baud_rate))
{
+ /* The requested speed could not be set. Error out to
+ top level after closing remote_desc. Take care to
+ set remote_desc to NULL to avoid closing remote_desc
+ more than once. */
serial_close (remote_desc);
+ remote_desc = NULL;
perror_with_name (name);
}
}
@@ -5552,7 +5557,12 @@ remote_cisco_open (char *name, int from_
baud_rate = (baud_rate > 0) ? baud_rate : 9600;
if (serial_setbaudrate (remote_desc, baud_rate))
{
+ /* The requested speed could not be set. Error out to
+ top level after closing remote_desc. Take care to
+ set remote_desc to NULL to avoid closing remote_desc
+ more than once. */
serial_close (remote_desc);
+ remote_desc = NULL;
perror_with_name (name);
}
next reply other threads:[~2003-12-05 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 20:36 Kevin Buettner [this message]
2003-12-05 21:04 ` Daniel Jacobowitz
2003-12-07 1:57 ` Andrew Cagney
2003-12-08 17:01 ` Kevin Buettner
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=1031205203631.ZM15513@localhost.localdomain \
--to=kevinb@redhat.com \
--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