Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>,
		"'Pedro Alves'" <pedro_alves@portugalmail.pt>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFA] Enhance stabs reader to better deal with forward 	references
Date: Mon, 02 Apr 2007 08:51:00 -0000	[thread overview]
Message-ID: <000001c77504$1a76a2d0$4f63e870$@u-strasbg.fr> (raw)
In-Reply-To: <20070402070011.GC3963@adacore.com>

  I made the same change to my local repository,
due to the same problem, on the same target.

  The problem is that in the CVS tree, end_symtab function
is called from within the read_ofile_symtab function
after current_objfile is reset to nil.
  But due to your change, current_objfile is still 
accessed inside dbx_lookup_type (stabsread.c)
called by cleanup_undefined_types_noname (stabsread.c)
called by cleanup_undefined_types (stabsread.c)
called by end_symtab (buildsym.c).


Hope this helps,

Pierre

-----Message d'origine-----
De : gdb-patches-owner@sourceware.org
[mailto:gdb-patches-owner@sourceware.org] De la part de Joel Brobecker
Envoyé : Monday, April 02, 2007 9:00 AM
À : Pedro Alves
Cc : gdb-patches@sourceware.org
Objet : Re: [RFA] Enhance stabs reader to better deal with forward
references

Pedro,

> Unfortunatelly, this patch broke Cygwin, which still uses stabs by
default.
> 
> I am getting a SIGSEGV while issuing a breakpoint.

Thanks for the report, and sorry about that. Unfortunately, I won't have
much time in the next two or three days - I might be able to understand
what is actually from the backtrace and your patch, but it might not be
sufficient. And if you have an opportunity to investigate a bit more,
that would be very much appreciated.  In the meantime, feel free to back
the patch out if necessary.

-- 
Joel




  reply	other threads:[~2007-04-02  8:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 19:40 Joel Brobecker
2007-02-27 16:50 ` Daniel Jacobowitz
2007-02-28  5:48   ` Joel Brobecker
2007-02-28 11:42     ` Daniel Jacobowitz
2007-02-28 20:12   ` Joel Brobecker
2007-03-27 16:29     ` Daniel Jacobowitz
2007-03-29 18:35       ` Joel Brobecker
2007-03-31 20:42         ` Pedro Alves
2007-04-02  6:59           ` Joel Brobecker
2007-04-02  8:51             ` Pierre Muller [this message]
2007-04-02 11:05           ` Daniel Jacobowitz
2007-04-03  0:13             ` Pedro Alves
2007-04-03  3:50               ` Christopher Faylor

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='000001c77504$1a76a2d0$4f63e870$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro_alves@portugalmail.pt \
    /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