Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@gnat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Klee Dienes <klee@apple.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] GDB crash when using command lines due to memory corruption
Date: Thu, 12 Dec 2002 02:04:00 -0000	[thread overview]
Message-ID: <20021212094232.GJ25575@gnat.com> (raw)
In-Reply-To: <3DF7C8AB.6822A575@redhat.com>

> > A safer change for 5.3 might be the patch I submitted on October 30th.
> > 
> >         http://sources.redhat.com/ml/gdb-patches/2002-10/msg00586.html
> > 
> 
> Joel, would Klee's change satisfy your requirement?

Absolutely. Klee's change is actually the first solution I came up with,
but for some reason I remembered that there was a reluctance to copy
this command lines structure more often than necessary. To be fair, I
really like Klee's change over mine, as it is much simpler and much more
maintainable. Can Klee's change be approved, and can Klee do the
checkin? I can also do the checkin on Klee's behalf if he's busy.
He's addition testcase is also a useful addition to our testsuite.

One small detail, is about memory management. Did anybody make sure that
there is no memory leak introduced in this change?

Speaking of memory leaks, there is the small change is
bpstat_stop_status which I will resubmit separately.

Thanks,
-- 
Joel


  reply	other threads:[~2002-12-12  9:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 10:01 Joel Brobecker
2002-12-11 10:20 ` Klee Dienes
2002-12-11 15:24   ` Michael Snyder
2002-12-12  2:04     ` Joel Brobecker [this message]
2002-12-12  2:41   ` Joel Brobecker
2002-12-12 13:03     ` Daniel Jacobowitz
2003-01-13  3:21   ` [RFA] (ping) " Joel Brobecker
2003-02-11  9:38     ` Joel Brobecker
2003-02-11 16:55       ` Andrew Cagney
2003-02-24  7:37         ` Andrew Cagney
2003-03-10 23:38   ` [RFC/RFA] " Daniel Jacobowitz

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=20021212094232.GJ25575@gnat.com \
    --to=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=klee@apple.com \
    --cc=msnyder@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