Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] remote.c: Avoid multiple serial_close calls on baud rate error
Date: Fri, 05 Dec 2003 21:04:00 -0000	[thread overview]
Message-ID: <20031205210441.GA10543@nevyn.them.org> (raw)
In-Reply-To: <1031205203631.ZM15513@localhost.localdomain>

On Fri, Dec 05, 2003 at 01:36:32PM -0700, Kevin Buettner wrote:
> 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

Coincidentally, one of my colleagues also recently noticed this :)
Thanks!

No comments on the patch itself, looks plausible.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-12-05 21:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05 20:36 Kevin Buettner
2003-12-05 21:04 ` Daniel Jacobowitz [this message]
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=20031205210441.GA10543@nevyn.them.org \
    --to=drow@mvista.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