From: Stephane Carrez <stcarrez@nerim.fr>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch rfc] use typedef opaque type implementations
Date: Thu, 13 Mar 2003 20:28:00 -0000 [thread overview]
Message-ID: <3E70E9F8.4020702@nerim.fr> (raw)
In-Reply-To: <3E623567.3060508@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
Hi Andrew,
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
>
Hum... yes. You broke the TUI because the following typedef:
> @@ -35,6 +36,7 @@
> int line;
> int start_of_line;
> };
> +struct ui_out_data tui_out_data;
>
is not a typedef but a global variable declaration :-)
I've committed this patch to fix the TUI.
Stephane
2003-03-13 Stephane Carrez <stcarrez@nerim.fr>
* tui-out.c (tui_out_data): Fix typedef.
[-- Attachment #2: tui-out.c.diffs --]
[-- Type: text/plain, Size: 468 bytes --]
Index: tui-out.c
===================================================================
RCS file: /cvs/src/src/gdb/tui/tui-out.c,v
retrieving revision 1.4
diff -u -p -r1.4 tui-out.c
--- tui-out.c 8 Mar 2003 20:04:27 -0000 1.4
+++ tui-out.c 13 Mar 2003 20:22:30 -0000
@@ -36,7 +36,7 @@ struct ui_out_data
int line;
int start_of_line;
};
-struct ui_out_data tui_out_data;
+typedef struct ui_out_data tui_out_data;
/* These are the CLI output functions */
prev parent reply other threads:[~2003-03-13 20:28 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
2003-03-07 19:17 ` Andrew Cagney
2003-03-08 19:37 ` Andrew Cagney
2003-03-13 20:28 ` Stephane Carrez [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=3E70E9F8.4020702@nerim.fr \
--to=stcarrez@nerim.fr \
--cc=ac131313@redhat.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