public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "muller at ics dot u-strasbg dot fr" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/11479] Stabs qualified function argument with opaque type not displayed correctly
Date: Fri, 23 Apr 2010 15:04:00 -0000	[thread overview]
Message-ID: <20100423150420.31662.qmail@sourceware.org> (raw)
In-Reply-To: <20100408161310.11479.muller@ics.u-strasbg.fr>


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2010-04-22 12:31 -------
Subject: Bug 11479

CVSROOT:	/cvs/src
Module name:	src
Changes by:	muller@sourceware.org	2010-04-22 12:30:55

Modified files:
	gdb            : ChangeLog stabsread.c 

Log message:
	PR stabs/11479.
	* stabsread.c (set_length_in_type_chain): New function.
	(read_struct_type): Call set_length_in_type_chain function.
	(read_enum_type): Idem.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/ChangeLog.diff?cvsroot=src&r1=1.11666&r2=1.11667
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/stabsread.c.diff?cvsroot=src&r1=1.124&r2=1.125


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2010-04-22 13:37 -------
Subject: Bug 11479

CVSROOT:	/cvs/src
Module name:	src
Changes by:	muller@sourceware.org	2010-04-22 13:37:18

Modified files:
	gdb/testsuite  : ChangeLog 
Added files:
	gdb/testsuite/gdb.stabs: gdb11479.c gdb11479.exp 

Log message:
	PR stabs/11479.
	* gdb.stabs/gdb11479.exp: New file.
	* gdb.stabs/gdb11479.c: New file.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/ChangeLog.diff?cvsroot=src&r1=1.2247&r2=1.2248
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/gdb.stabs/gdb11479.c.diff?cvsroot=src&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/gdb.stabs/gdb11479.exp.diff?cvsroot=src&r1=NONE&r2=1.1


------- Additional Comments From muller at ics dot u-strasbg dot fr  2010-04-23 15:04 -------
 Fixed by the commits from 2010/04/22
listed.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED
            Summary|Stabs qualified function    |Stabs qualified function
                   |argument with opaque type   |argument with opaque type
                   |not dispalyed correctly     |not displayed correctly
   Target Milestone|7.1                         |7.2


http://sourceware.org/bugzilla/show_bug.cgi?id=11479

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


      reply	other threads:[~2010-04-23 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08 16:13 [Bug symtab/11479] New: Stabs qualified function argument with opaque type not dispalyed correctly muller at ics dot u-strasbg dot fr
2010-04-23 15:04 ` muller at ics dot u-strasbg dot fr [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=20100423150420.31662.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).