Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Tom Tromey'" <tromey@redhat.com>
Cc: "'Tristan Gingold'" <gingold@adacore.com>, <gdb-patches@sourceware.org>
Subject: RE: [RFC] Improve stabs debugging for mingw64 executables loaded at high addresses
Date: Wed, 15 Sep 2010 11:54:00 -0000	[thread overview]
Message-ID: <001a01cb54b0$2b2e4120$818ac360$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <m3lj748a4p.fsf@fleche.redhat.com>



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Tom Tromey
> Envoyé : Tuesday, September 14, 2010 8:15 PM
> À : Pierre Muller
> Cc : 'Tristan Gingold'; gdb-patches@sourceware.org
> Objet : Re: [RFC] Improve stabs debugging for mingw64 executables
> loaded at high addresses
> 
> >>>>> "Pierre" == Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
> writes:
> 
> Pierre>   The thing is that, for Free Pascal, we have lots of
> Pierre> troubles with DWARF (and some 64-bit specific),
> 
> Can we also fix that somehow?

  I hope to work on it, but starting with
usable stabs debug info to debug dwarf debug info problems
would make life much more easy.

Pierre


  reply	other threads:[~2010-09-15  8:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14 17:15 Pierre Muller
2010-09-14 17:32 ` Tristan Gingold
2010-09-14 17:50   ` Pierre Muller
2010-09-15  8:30     ` Tristan Gingold
2010-09-15  8:33       ` Pierre Muller
2010-09-15 12:42         ` Tristan Gingold
     [not found]   ` <47535.3697002449$1284477885@news.gmane.org>
2010-09-14 20:56     ` Tom Tromey
2010-09-15 11:54       ` Pierre Muller [this message]
2010-09-14 18:15 ` Michael Snyder
2010-09-14 19:07   ` Joel Brobecker
2010-09-15  9:57     ` 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='001a01cb54b0$2b2e4120$818ac360$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=gdb-patches@sourceware.org \
    --cc=gingold@adacore.com \
    --cc=tromey@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