Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: randolph@tausq.org, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Don't unwind past entry point
Date: Wed, 10 Nov 2004 20:47:00 -0000	[thread overview]
Message-ID: <01c4c764$Blat.v2.2.2$d7e3bce0@zahav.net.il> (raw)
In-Reply-To: <41924990.9060504@gnu.org> (message from Andrew Cagney on Wed, 10 Nov 2004 12:02:08 -0500)

> Date: Wed, 10 Nov 2004 12:02:08 -0500
> From: Andrew Cagney <cagney@gnu.org>
> Cc: gdb-patches@sources.redhat.com
> 
> Check eli for the doco.

Thanks for the heads-up, I missed the original message.

>  @table @code
>  @item set backtrace past-main
>  @itemx set backtrace past-main on
> -@kindex set backtrace
> +@kindex set backtrace past-main

Please don't make this change.  When there are several commands that
begin with the same string, like "set backtrace SOMETHING" which all
begin with "set backtrace", we should always index only the common
part and do it only once, so that we end up with a single index entry
that points to the place where the whole family is described.

So please leave only the original "@kindex set backtrace" and "@kindex
show backtrace" entries, and remove all the rest.

> -@kindex show backtrace
> +@kindex show backtrace past-main

This change should also be undone.

> +This entry point is encoded by the linker when the application is built,
> +and is likely before the user entry point ``main'' (or equivalent) is called.

Please use @code{main}, without any quotes.  This produces `main' in
the Info manual and uses an appropriate typeface in the printed
version.

Otherwise, the doco patch is fine.  Thanks.


      parent reply	other threads:[~2004-11-10 20:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-09 19:24 Randolph Chung
2004-11-10 17:03 ` Andrew Cagney
2004-11-10 17:07   ` Randolph Chung
2004-11-10 18:13     ` Paul Gilliam
2004-11-10 20:47   ` Eli Zaretskii [this message]

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='01c4c764$Blat.v2.2.2$d7e3bce0@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=randolph@tausq.org \
    /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