Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb <gdb@sources.redhat.com>
Subject: mdebugread.c (was Re: struct environment)
Date: Fri, 06 Sep 2002 14:57:00 -0000	[thread overview]
Message-ID: <ro1u1l2bx5f.fsf_-_@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20020906214632.GA29724@nevyn.them.org>

On Fri, 6 Sep 2002 17:46:32 -0400, Daniel Jacobowitz <drow@mvista.com> said:
> On Fri, Sep 06, 2002 at 02:41:02PM -0700, David Carlton wrote:

>> How hard do you think it would be to convert mdebugread over to using
>> the mechanisms from buildsym?

> I think, very easy.  But I no longer have (easy) access to any system
> which uses it, so I was reluctant to mess around.

Yeah, that's something that I'm worried about too.  Is there anybody
else that's reading this that can help with changes to that file?
Who's the appropriate maintainer; is it Andrew?

David Carlton
carlton@math.stanford.edu


  reply	other threads:[~2002-09-06 21:57 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05 13:50 struct environment David Carlton
2002-09-06  8:06 ` Daniel Jacobowitz
2002-09-06 10:20   ` David Carlton
2002-09-06 10:57     ` Daniel Jacobowitz
2002-09-06 11:56       ` David Carlton
2002-09-06 12:34         ` Daniel Berlin
2002-09-06 12:41           ` Daniel Jacobowitz
2002-09-06 12:55             ` Daniel Berlin
2002-09-11 11:33         ` David Carlton
2002-09-11 11:36           ` Daniel Jacobowitz
2002-09-11 12:27             ` David Carlton
2002-09-06 14:43   ` David Carlton
2002-09-06 14:46     ` Daniel Jacobowitz
2002-09-06 14:57       ` David Carlton [this message]
2002-09-06 15:35         ` mdebugread.c (was Re: struct environment) Daniel Jacobowitz
2002-09-10 17:25   ` struct environment David Carlton
2002-09-10 17:31     ` Daniel Jacobowitz
2002-09-11 10:29       ` David Carlton
2002-09-11 10:55         ` Daniel Jacobowitz
2002-09-11 12:33         ` Daniel Berlin
2002-09-10 17:36     ` David Carlton
2002-09-16 22:03   ` Andrew Cagney
2002-09-06 15:00 ` David Carlton
2002-09-06 16:37   ` Tom Tromey
2002-09-06 17:19     ` David Carlton
2002-09-07 10:26       ` Per Bothner
2002-09-07 10:32         ` Daniel Jacobowitz
2002-09-09 11:18           ` David Carlton
2002-09-12 12:26 ` Andrew Cagney
2002-09-13  9:44   ` David Carlton
2002-09-17  0:48 ` Andrew Cagney
2002-09-17  6:41   ` Daniel Jacobowitz
2002-09-17  8:59     ` Andrew Cagney
2002-09-17  9:07       ` Daniel Jacobowitz
2002-09-17 10:54         ` Andrew Cagney
2002-09-17 11:02           ` Daniel Jacobowitz
2002-09-17 12:37             ` Andrew Cagney
2002-09-17 12:41               ` Daniel Jacobowitz
2002-09-18  8:13                 ` Andrew Cagney
2002-09-17 12:52             ` Daniel Berlin
2002-09-17 13:34               ` Daniel Jacobowitz
2002-09-17 21:51                 ` Daniel Berlin
2002-09-18  7:26                   ` Daniel Jacobowitz
2002-09-18  9:08                   ` David Carlton
2002-09-17 12:18     ` David Carlton
2002-09-17 10:29   ` David Carlton
2002-09-17 12:50     ` Daniel Berlin
2002-09-17 13:24       ` David Carlton
2002-09-18 22:26 ` 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=ro1u1l2bx5f.fsf_-_@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.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