Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Ton van Overbeek <v-overbeek@cistron.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix coff symbol table reading problem for C code compiled by g++
Date: Sat, 14 Aug 2004 11:36:00 -0000	[thread overview]
Message-ID: <7137-Sat14Aug2004143240+0300-eliz@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0408130200490.24052@picard.cistron.nl> (message from Ton van Overbeek on Fri, 13 Aug 2004 02:06:00 +0200 (CEST))

> Date: Fri, 13 Aug 2004 02:06:00 +0200 (CEST)
> From: Ton van Overbeek <v-overbeek@cistron.nl>
> 
> I found a bug/problem in the symbol reading code in symtab.c in gdb-6.2.

Thanks for the report and the patch.

Could you please also provide a short test case and an example
compile-link-GDB session script which both shows how to eproduce the
problem and the exact outputs from GDB?

TIA


  reply	other threads:[~2004-08-14 11:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13  0:06 Ton van Overbeek
2004-08-14 11:36 ` Eli Zaretskii [this message]
2004-08-15  0:29   ` Ton van Overbeek
2004-08-21 12:19     ` Eli Zaretskii
2004-09-16  0:23 ` Jim Blandy

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=7137-Sat14Aug2004143240+0300-eliz@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=v-overbeek@cistron.nl \
    /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