Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@elta.co.il>
To: Andrew Cagney <cagney@gnu.org>
Cc: 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: <un06e7kia.fsf@elta.co.il> (raw)
In-Reply-To: <4058B42C.8010007@gnu.org> (message from Andrew Cagney on Wed, 17 Mar 2004 15:25:16 -0500)

> Date: Wed, 17 Mar 2004 15:25:16 -0500
> From: Andrew Cagney <cagney@gnu.org>
> 
> - arches using the old frame stuff are typically in worse shape

I don't think we can tell users their target is ``in worse shape''
without being specific.  It sounds like FUD, even though I realize it
isn't.  If we want to tell users their target suffers from problems,
we should make the effort of spelling out those problems in terms
users can understand and act upon.

> - 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).

This is IMHO better than just ``in worse shape'', but it's still not
detailed enough.  I, for one, don't understand the real meaning of
``decent backtraces''.  What does it mean? do I get garbage in some or
all frames? does the backtrace stop short of showing be the whole
picture? which frames are susceptible and what can I do to alleviate
that (compilation options, perhaps)?  Etc., etc.

Also, are there actually targets that use the old frame stuff _and_
use glibc?  (It strikes me that the crazy techniques used by glibc are
as guilty for breaking GDB as the oldish targets.)


WARNING: multiple messages have this Message-ID
From: Eli Zaretskii <eliz@elta.co.il>
To: Andrew Cagney <cagney@gnu.org>
Cc: carlton@kealia.com,mec.gnu@mindspring.com,gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0
Date: Thu, 18 Mar 2004 06:11:00 -0000	[thread overview]
Message-ID: <un06e7kia.fsf@elta.co.il> (raw)
Message-ID: <20040318061100.oPDcUk8gjw9jNToka9BpeuvRPex8fuA3YRrthbkb9zc@z> (raw)
In-Reply-To: <4058B42C.8010007@gnu.org> (message from Andrew Cagney on Wed, 17 Mar 2004 15:25:16 -0500)

> Date: Wed, 17 Mar 2004 15:25:16 -0500
> From: Andrew Cagney <cagney@gnu.org>
> 
> - arches using the old frame stuff are typically in worse shape

I don't think we can tell users their target is ``in worse shape''
without being specific.  It sounds like FUD, even though I realize it
isn't.  If we want to tell users their target suffers from problems,
we should make the effort of spelling out those problems in terms
users can understand and act upon.

> - 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).

This is IMHO better than just ``in worse shape'', but it's still not
detailed enough.  I, for one, don't understand the real meaning of
``decent backtraces''.  What does it mean? do I get garbage in some or
all frames? does the backtrace stop short of showing be the whole
picture? which frames are susceptible and what can I do to alleviate
that (compilation options, perhaps)?  Etc., etc.

Also, are there actually targets that use the old frame stuff _and_
use glibc?  (It strikes me that the crazy techniques used by glibc are
as guilty for breaking GDB as the oldish targets.)


  parent reply	other threads:[~2004-03-18  6: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 ` 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     ` David Carlton
2004-03-17 19:18       ` David Carlton
2004-03-19  0:09     ` Andrew Cagney
2004-03-17 22:11       ` Andrew Cagney
2004-03-19  0:09       ` Eli Zaretskii [this message]
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 ` Michael Elizabeth Chastain
2004-03-19  0:09 ` Eli Zaretskii
2004-03-17  6:16   ` Eli Zaretskii
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-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
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-18 16:23 ` Michael Elizabeth Chastain
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 ` David Carlton
2004-03-18 16:45   ` David Carlton
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17  6:58 ` Michael Elizabeth Chastain

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=un06e7kia.fsf@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=cagney@gnu.org \
    --cc=carlton@kealia.com \
    --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