From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch rfc] use typedef opaque type implementations
Date: Sun, 02 Mar 2003 18:35:00 -0000 [thread overview]
Message-ID: <20030302183550.GA21343@nevyn.them.org> (raw)
In-Reply-To: <3E623567.3060508@redhat.com>
On Sun, Mar 02, 2003 at 11:46:31AM -0500, Andrew Cagney wrote:
> This patch follows up an earlier thread that pointed out that GDB is
> pretty broken when it comes to debugging a program that contains
> multiple struct definitions (e.g., gdb).
>
> The attached patch implements the suggested `fix'. Declare a file-local
> typedef and then use that. I've applied it to the ui-out code. A quick
> debug suggests that it works well.
>
> comments? I'll table this for a week ...
> Andrew
I assume GDB handles this correctly - if not, it's a fixable bug in the
debug readers, presumably. Looks like as elegant a solution as I could
have asked for.
Should we put something about this in the coding standards?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-03-02 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 17:18 Andrew Cagney
2003-03-02 18:35 ` Daniel Jacobowitz [this message]
2003-03-07 19:17 ` Andrew Cagney
2003-03-08 19:37 ` Andrew Cagney
2003-03-13 20:28 ` Stephane Carrez
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=20030302183550.GA21343@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@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