From: Daniel Jacobowitz <drow@mvista.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: gdb@sources.redhat.com
Subject: Re: 6.0 BUG? SIGSEGV under cygwin
Date: Tue, 15 Jul 2003 14:52:00 -0000 [thread overview]
Message-ID: <20030715145158.GA29718@nevyn.them.org> (raw)
In-Reply-To: <5.0.2.1.2.20030715162155.04307e60@ics.u-strasbg.fr>
On Tue, Jul 15, 2003 at 04:40:56PM +0200, Pierre Muller wrote:
> I compiled the 6.0 branch GDB
> with -gstabs+ debug option.
>
> I think that there is a problem
> in the current main and 6.0 branches,
> regarding use of sym_private file of struct objfile.
>
> This field is used to stored two incompatible
> things :
> in dwarf2-frame.c it is assumed that
> this field contains a struct dwarf2_fde pointer,
> but the same field is also used in
> coffread.c and xcoffread.c
> to store a struct coff_symfile_info pointer.
Mark Kettenis posted a patch for this just a few days ago on
gdb-patches. Would you test it? See:
Subject: [RFC/RFA] Per-objfile data mechanism
From Sunday.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-07-15 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 14:49 Pierre Muller
2003-07-15 14:52 ` Daniel Jacobowitz [this message]
2003-07-15 15:06 ` Pierre Muller
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=20030715145158.GA29718@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=muller@ics.u-strasbg.fr \
/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