Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@cygnus.com>
To: john@feith.com
Cc: gdb-patches@cygnus.com
Subject: Re: GDB 4.17 Patch for stack aligned i386 code
Date: Tue, 09 Mar 1999 18:04:00 -0000	[thread overview]
Message-ID: <199903100203.SAA12404@andros.cygnus.com> (raw)
In-Reply-To: <199903100107.UAA27933@jwlab.FEITH.COM>

   Date: Tue, 9 Mar 1999 20:07:11 -0500 (EST)
   From: John Wehle <john@feith.com>

   Did you receive the consolidated patch okay and is there anything else
   I need to do at this point in order have this integrated into gdb?
   Ideally I'd like this to be included in the next official release. :-)

Yes we did get it OK, thanx.  Jim B is signed up to look at it more
closely.  I have a bit of anxiety over including it in 4.18 at this
late date, because of the potential impact on all x86 configs.  Has
anybody else tried out this particular patch?

							Stan



WARNING: multiple messages have this Message-ID
From: Stan Shebs <shebs@cygnus.com>
To: john@feith.com
Cc: gdb-patches@cygnus.com
Subject: Re: GDB 4.17 Patch for stack aligned i386 code
Date: Thu, 01 Apr 1999 00:00:00 -0000	[thread overview]
Message-ID: <199903100203.SAA12404@andros.cygnus.com> (raw)
Message-ID: <19990401000000.XlLJo-8NcS6_ds3P9aXqzI_VXHPLI5F2HIHb5pNZ_Ec@z> (raw)
In-Reply-To: <199903100107.UAA27933@jwlab.FEITH.COM>

   Date: Tue, 9 Mar 1999 20:07:11 -0500 (EST)
   From: John Wehle <john@feith.com>

   Did you receive the consolidated patch okay and is there anything else
   I need to do at this point in order have this integrated into gdb?
   Ideally I'd like this to be included in the next official release. :-)

Yes we did get it OK, thanx.  Jim B is signed up to look at it more
closely.  I have a bit of anxiety over including it in 4.18 at this
late date, because of the potential impact on all x86 configs.  Has
anybody else tried out this particular patch?

							Stan



  parent reply	other threads:[~1999-03-09 18:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-01  0:00 John Wehle
1999-03-09 17:07 ` John Wehle
1999-03-09 18:04 ` Stan Shebs [this message]
1999-04-01  0:00   ` Stan Shebs
     [not found] <200003250030.TAA14328@jwlab.FEITH.COM>
2000-03-24 16:54 ` nsd
     [not found] <200003242355.SAA14221@jwlab.FEITH.COM>
2000-03-24 16:08 ` nsd
  -- strict thread matches above, loose matches on Subject: below --
1999-04-01  0:00 John Wehle
1999-01-20 22:33 ` John Wehle
1999-04-01  0:00 John Wehle
1999-02-24 19:41 ` John Wehle
1999-04-01  0:00 ` Stan Shebs
1999-02-24 19:41   ` Stan Shebs
1999-04-01  0:00 John Wehle
1999-03-09 18:39 ` John Wehle
1999-04-01  0:00 ` Stan Shebs
1999-03-09 18:57   ` Stan Shebs
1999-04-01  0:00 John Wehle
1999-02-25 20:48 ` John Wehle
1999-03-09 18:53 John Wehle
1999-04-01  0:00 ` John Wehle

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=199903100203.SAA12404@andros.cygnus.com \
    --to=shebs@cygnus.com \
    --cc=gdb-patches@cygnus.com \
    --cc=john@feith.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