public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Syd Polk <spolk@redhat.com>
Cc: insight@sources.redhat.com
Subject: Re: Buffer Overflow Patch in GDB/TCL Interface code.
Date: Thu, 19 Oct 2000 09:27:00 -0000	[thread overview]
Message-ID: <39EF20E4.17B86DFE@cygnus.com> (raw)
In-Reply-To: <39EF1F66.6D763F7F@redhat.com>

Syd Polk wrote:
> 
> My only concern is whether this call, asprintf, is available on all platforms.
> 

As gdb already uses it, it must be available at least where gdb is available.
This should suffice for us.


-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@cygnus.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

  reply	other threads:[~2000-10-19  9:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-19  6:30 Fernando Nasser
2000-10-19  9:17 ` Syd Polk
2000-10-19  9:27   ` Fernando Nasser [this message]
2000-10-19 11:26     ` Syd Polk
2000-10-20  8:42       ` Liberty, asprintf(), malloc() Fernando Nasser
2000-10-19 17:50   ` Buffer Overflow Patch in GDB/TCL Interface code Mike A. Harris
     [not found] <39EE5ED1.2CDECCDB@ozemail.com.au>
2000-10-19  6:20 ` Fernando Nasser

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=39EF20E4.17B86DFE@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=insight@sources.redhat.com \
    --cc=spolk@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).