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: <199903100257.SAA12491@andros.cygnus.com> (raw)
In-Reply-To: <199903100239.VAA28392@jwlab.FEITH.COM>
Date: Tue, 9 Mar 1999 21:39:28 -0500 (EST)
From: John Wehle <john@feith.com>
> 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.
Understandable. What the time frame for the 4.18 release? Any
idea of the rough plan for a follow up release?
4.18 should be finished this month, unless some kind of huge
showstopper materializes. I'd like the next release to happen in less
than a year, with all the current goings-on, once/year is a little too
slow of a pace.
1) Backtracing through sigtramps on Solaris is somewhat busted without
my changes (the Solaris library contains functions which don't use
%ebp as the frame pointer). For example ... the backtrace from
gdb.base/a1-selftest.exp (without my patch) shows:
Hmmm, that makes it a bug fix, not a new feature, therefore more
important to add! 1/2 :-)
2) The egcs patch to eliminate the frame pointer by default on the
x86 can't be installed until there's debugger support.
That's a pretty compelling point too. I'm kind of tempted to go for
this change...
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: Tue, 09 Mar 1999 18:57:00 -0000 [thread overview]
Message-ID: <199903100257.SAA12491@andros.cygnus.com> (raw)
Message-ID: <19990309185700.J0G41iFuF8okX3Ae-HHUf3QgTM9rZtSZ6utzBsx51GE@z> (raw)
In-Reply-To: <199903100239.VAA28392@jwlab.FEITH.COM>
Date: Tue, 9 Mar 1999 21:39:28 -0500 (EST)
From: John Wehle <john@feith.com>
> 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.
Understandable. What the time frame for the 4.18 release? Any
idea of the rough plan for a follow up release?
4.18 should be finished this month, unless some kind of huge
showstopper materializes. I'd like the next release to happen in less
than a year, with all the current goings-on, once/year is a little too
slow of a pace.
1) Backtracing through sigtramps on Solaris is somewhat busted without
my changes (the Solaris library contains functions which don't use
%ebp as the frame pointer). For example ... the backtrace from
gdb.base/a1-selftest.exp (without my patch) shows:
Hmmm, that makes it a bug fix, not a new feature, therefore more
important to add! 1/2 :-)
2) The egcs patch to eliminate the frame pointer by default on the
x86 can't be installed until there's debugger support.
That's a pretty compelling point too. I'm kind of tempted to go for
this change...
Stan
next prev parent reply other threads:[~1999-04-01 0:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-01 0:00 John Wehle
1999-03-09 18:39 ` John Wehle
1999-04-01 0:00 ` Stan Shebs [this message]
1999-03-09 18:57 ` 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-02-25 20:48 ` John Wehle
1999-04-01 0:00 John Wehle
1999-01-20 22:33 ` John Wehle
1999-04-01 0:00 John Wehle
1999-03-09 17:07 ` John Wehle
1999-03-09 18:04 ` Stan Shebs
1999-04-01 0:00 ` Stan Shebs
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-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=199903100257.SAA12491@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