Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Wehle <john@feith.com>
To: shebs@cygnus.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: <199903100239.VAA28392@jwlab.FEITH.COM> (raw)

> 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? My concerns are:

  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:

#0  0x80068745 in _libc_sigprocmask ()
#1  0x80098763 in sigprocmask ()
#2  0x8107cb3 in rl_signal_handler (sig=134509072) at signals.c:156
#3  0x800685b1 in _sigacthandler ()
#4  <signal handler called>
#5  0x800682b8 in _libc_read ()
#6  0x8101ef9 in rl_getc (stream=0x800a9ad4) at readline.c:3123
#7  0x80ffa5b in rl_read_key () at readline.c:578

     The correct backtrace is:

#0  0x80068745 in _libc_sigprocmask ()
#1  0x80098763 in sigprocmask ()
#2  0x8107fe7 in rl_signal_handler (sig=134509096) at signals.c:156
#3  0x800685b1 in _sigacthandler ()
#4  <signal handler called>
#5  0x800682b8 in _libc_read ()
#6  0x80098b33 in read ()
#7  0x810222d in rl_getc (stream=0x81639a0) at readline.c:3123
#8  0x80ffd8f in rl_read_key () at readline.c:578

  2) The egcs patch to eliminate the frame pointer by default on the
     x86 can't be installed until there's debugger support.

I certainly agree that this is a sizable change to the x86 support and
realize that it may not make sense for 4.18 if you guys are close to a
release.  Drat. :-)

-- John
-------------------------------------------------------------------------
|   Feith Systems  |   Voice: 1-215-646-8000  |  Email: john@feith.com  |
|    John Wehle    |     Fax: 1-215-540-5495  |                         |
-------------------------------------------------------------------------



WARNING: multiple messages have this Message-ID
From: John Wehle <john@feith.com>
To: shebs@cygnus.com
Cc: gdb-patches@cygnus.com
Subject: Re: GDB 4.17 Patch for stack aligned i386 code
Date: Tue, 09 Mar 1999 18:39:00 -0000	[thread overview]
Message-ID: <199903100239.VAA28392@jwlab.FEITH.COM> (raw)
Message-ID: <19990309183900.yk7e1AxQZUOUDAfulu5IDxJ2S97d-9hF5N1oj6He8Mk@z> (raw)

> 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? My concerns are:

  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:

#0  0x80068745 in _libc_sigprocmask ()
#1  0x80098763 in sigprocmask ()
#2  0x8107cb3 in rl_signal_handler (sig=134509072) at signals.c:156
#3  0x800685b1 in _sigacthandler ()
#4  <signal handler called>
#5  0x800682b8 in _libc_read ()
#6  0x8101ef9 in rl_getc (stream=0x800a9ad4) at readline.c:3123
#7  0x80ffa5b in rl_read_key () at readline.c:578

     The correct backtrace is:

#0  0x80068745 in _libc_sigprocmask ()
#1  0x80098763 in sigprocmask ()
#2  0x8107fe7 in rl_signal_handler (sig=134509096) at signals.c:156
#3  0x800685b1 in _sigacthandler ()
#4  <signal handler called>
#5  0x800682b8 in _libc_read ()
#6  0x80098b33 in read ()
#7  0x810222d in rl_getc (stream=0x81639a0) at readline.c:3123
#8  0x80ffd8f in rl_read_key () at readline.c:578

  2) The egcs patch to eliminate the frame pointer by default on the
     x86 can't be installed until there's debugger support.

I certainly agree that this is a sizable change to the x86 support and
realize that it may not make sense for 4.18 if you guys are close to a
release.  Drat. :-)

-- John
-------------------------------------------------------------------------
|   Feith Systems  |   Voice: 1-215-646-8000  |  Email: john@feith.com  |
|    John Wehle    |     Fax: 1-215-540-5495  |                         |
-------------------------------------------------------------------------



             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 [this message]
1999-03-09 18:39 ` John Wehle
1999-04-01  0:00 ` Stan Shebs
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-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-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=199903100239.VAA28392@jwlab.FEITH.COM \
    --to=john@feith.com \
    --cc=gdb-patches@cygnus.com \
    --cc=shebs@cygnus.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