Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: David Carlton <carlton@kealia.com>,
	mec.gnu@mindspring.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <4058B42C.8010007@gnu.org> (raw)
In-Reply-To: <8296-Wed17Mar2004210500+0200-eliz@elta.co.il>

>>From: David Carlton <carlton@kealia.com>
>>> Date: Wed, 17 Mar 2004 09:19:23 -0800
>>> 
>>> While we're updating PROBLEMS, is the list of targets that don't use
>>> the new frame code accurate?  (Sparc, mips, ppc, arm.)
> 
> 
> Do users care?  What user-level effect will one see on those targets
> that don't use the new frame code?
> 
> IMHO, if there are no user-level issues, we shouldn't mention this in
> PROBLEMS.

- arches using the old frame stuff are typically in worse shape
- arches using the old frame stuff can't use CFI (i.e., can't use 
exploit GCC's frame debug info)

the second one in particular is of issue to users - it affects GDB's 
ability to do decent backtraces (especially through glibc).

Yes, the list needs updating, SPARC and ARM are done.  MIPS and PA are 
"done" (it lost the signal stuff).  For PPC, that will be 6.2, which 
leaves a few strays.

Andrew



WARNING: multiple messages have this Message-ID
From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: David Carlton <carlton@kealia.com>,
	mec.gnu@mindspring.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0
Date: Wed, 17 Mar 2004 22:11:00 -0000	[thread overview]
Message-ID: <4058B42C.8010007@gnu.org> (raw)
Message-ID: <20040317221100.-DtR7jdI1O47Qch-px_xvBGqtujtm__UVAsAoatqtLg@z> (raw)
In-Reply-To: <8296-Wed17Mar2004210500+0200-eliz@elta.co.il>

>>From: David Carlton <carlton@kealia.com>
>>> Date: Wed, 17 Mar 2004 09:19:23 -0800
>>> 
>>> While we're updating PROBLEMS, is the list of targets that don't use
>>> the new frame code accurate?  (Sparc, mips, ppc, arm.)
> 
> 
> Do users care?  What user-level effect will one see on those targets
> that don't use the new frame code?
> 
> IMHO, if there are no user-level issues, we shouldn't mention this in
> PROBLEMS.

- arches using the old frame stuff are typically in worse shape
- arches using the old frame stuff can't use CFI (i.e., can't use 
exploit GCC's frame debug info)

the second one in particular is of issue to users - it affects GDB's 
ability to do decent backtraces (especially through glibc).

Yes, the list needs updating, SPARC and ARM are done.  MIPS and PA are 
"done" (it lost the signal stuff).  For PPC, that will be 6.2, which 
leaves a few strays.

Andrew



  parent reply	other threads:[~2004-03-17 22:11 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17  1:53 Michael Elizabeth Chastain
2004-03-17 16:13 ` Andrew Cagney
2004-03-19  0:09   ` Andrew Cagney
2004-03-17 17:05 ` David Carlton
2004-03-19  0:09   ` David Carlton
2004-03-19  0:09 ` Eli Zaretskii
2004-03-17  6:16   ` Eli Zaretskii
2004-03-19  0:09 ` David Carlton
2004-03-17 17:19   ` David Carlton
2004-03-19  0:09   ` Eli Zaretskii
2004-03-17 19:07     ` Eli Zaretskii
2004-03-19  0:09     ` Andrew Cagney [this message]
2004-03-17 22:11       ` Andrew Cagney
2004-03-19  0:09       ` Eli Zaretskii
2004-03-18  6:11         ` Eli Zaretskii
2004-03-18 16:36         ` Daniel Jacobowitz
2004-03-19  0:09           ` Eli Zaretskii
2004-03-18 16:55             ` Eli Zaretskii
2004-03-19  0:09           ` Daniel Jacobowitz
2004-03-19  0:09           ` Andrew Cagney
2004-03-19  0:25             ` Daniel Jacobowitz
2004-03-19  0:09     ` David Carlton
2004-03-17 19:18       ` David Carlton
2004-03-19  0:09 ` Michael Elizabeth Chastain
2004-03-17 18:55 Michael Elizabeth Chastain
2004-03-17 19:03 ` David Carlton
2004-03-19  0:09   ` David Carlton
2004-03-19  0:09 ` Michael Elizabeth Chastain
2004-03-19  0:09 ` David Carlton
2004-03-17 19:16   ` David Carlton
2004-03-17 22:54 Michael Elizabeth Chastain
2004-03-17 23:39 ` Andrew Cagney
2004-03-18  6:16   ` Eli Zaretskii
2004-03-18 16:05     ` Andrew Cagney
2004-03-18 16:52       ` Eli Zaretskii
2004-03-19  0:09         ` Eli Zaretskii
2004-03-19  0:09       ` Andrew Cagney
2004-03-19  0:09     ` Eli Zaretskii
2004-03-19  0:09   ` Andrew Cagney
2004-03-19  0:09 ` Michael Elizabeth Chastain
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-18 16:23 ` Michael Elizabeth Chastain
2004-03-19  0:09 ` David Carlton
2004-03-18 16:45   ` David Carlton
2004-03-19  0:09 ` Andrew Cagney
2004-03-19  0:27   ` Daniel Jacobowitz
2004-03-19 14:56     ` Eli Zaretskii
2004-03-19 15:03     ` Andrew Cagney
2004-03-19 15:33       ` Eli Zaretskii
2004-03-19 15:54         ` Andrew Cagney
2004-03-20 15:38           ` Eli Zaretskii
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17  6:58 ` Michael Elizabeth Chastain
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17 19:30 ` Michael Elizabeth Chastain
2004-03-17 19:48 ` David Carlton
2004-03-19  0:09   ` David Carlton
2004-03-19  0:09   ` Eli Zaretskii
2004-03-18  6:06     ` Eli Zaretskii
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17 20:15 ` Michael Elizabeth Chastain
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17 19:21 ` Michael Elizabeth Chastain
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17 18:21 ` Michael Elizabeth Chastain
2004-03-17 22:11 ` Andrew Cagney
2004-03-19  0:09   ` Andrew Cagney

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=4058B42C.8010007@gnu.org \
    --to=cagney@gnu.org \
    --cc=carlton@kealia.com \
    --cc=eliz@elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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