Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: ngustavson@emacinc.com, gdb-patches@sourceware.org
Subject: Re: gdb code review, pointer madness
Date: Wed, 25 Jan 2006 19:58:00 -0000	[thread overview]
Message-ID: <ur76wdqt0.fsf@gnu.org> (raw)
In-Reply-To: <8f2776cb0601251049h742c3a20rf7f5f3f062888a1c@mail.gmail.com> 	(message from Jim Blandy on Wed, 25 Jan 2006 10:49:25 -0800)

> Date: Wed, 25 Jan 2006 10:49:25 -0800
> From: Jim Blandy <jimb@red-bean.com>
> Cc: ngustavson@emacinc.com, gdb-patches@sourceware.org
> 
> On 1/25/06, Eli Zaretskii <eliz@gnu.org> wrote:
> > > Date: Tue, 24 Jan 2006 21:25:44 -0800
> > > From: Jim Blandy <jimb@red-bean.com>
> > > Cc: ngustavson@emacinc.com, gdb-patches@sourceware.org
> > >
> > > I'm being lazy.  How's this?
> >
> > Almost perfect.  If you add a "@cindex sentinel frame" and a
> > "@findex frame_register_unwind", it will be _just_ perfect.
> >
> > Actually, maybe also "@cindex frame, unwind".
> 
> I've committed the below, adding @vindex SENTINEL_FRAME:

Thanks.


  reply	other threads:[~2006-01-25 19:58 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23 20:39 NZG
2006-01-23 20:48 ` Daniel Jacobowitz
2006-01-23 20:51 ` Jim Blandy
2006-01-24 17:19   ` NZG
2006-01-24 19:29     ` NZG
2006-01-24 21:27       ` Jim Blandy
2006-01-24 21:58         ` NZG
2006-01-24 22:11           ` Daniel Jacobowitz
2006-01-25  0:01           ` Jim Blandy
2006-01-25  4:41             ` Eli Zaretskii
2006-01-25  4:59               ` Jim Blandy
2006-01-25  5:25                 ` Jim Blandy
2006-01-25 17:21                   ` Eli Zaretskii
2006-01-25 18:49                     ` Jim Blandy
2006-01-25 19:58                       ` Eli Zaretskii [this message]
2006-01-25 17:15                 ` Eli Zaretskii
2006-01-26 16:19             ` NZG
2006-01-26 16:43               ` Daniel Jacobowitz
2006-01-26 19:55                 ` frame theory, was " NZG
2006-01-26 19:59                   ` Daniel Jacobowitz
2006-01-26 20:17                     ` NZG
2006-01-26 20:22                       ` Daniel Jacobowitz
2006-01-26 21:21                   ` Mark Kettenis
2006-01-26 21:54                     ` NZG
2006-01-26 22:40                       ` Mark Kettenis
2006-01-26 22:44                         ` Daniel Jacobowitz
2006-01-26 23:27                           ` remote connection crash, was frame theory NZG
2006-01-26 23:32                             ` Daniel Jacobowitz
2006-01-26 23:42                             ` Jim Blandy
2006-01-26 23:45                               ` Daniel Jacobowitz
2006-01-26 23:57                                 ` Jim Blandy
2006-01-27  0:04                                   ` NZG
2006-01-30 17:02                                     ` 5282 gdb Eclipse MI support, was remote connection crash NZG
2006-01-26 23:47                           ` frame theory, was pointer madness Accounts
2006-01-26 23:16                   ` Jim Blandy
2006-01-26 23:39                     ` Jim Blandy
2006-01-27  7:19                     ` Eli Zaretskii

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=ur76wdqt0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@red-bean.com \
    --cc=ngustavson@emacinc.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