From: Pedro Alves <pedro_alves@portugalmail.pt>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: 'Joel Brobecker' <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] ARI fix: Remove asprintf in breakpoint.c
Date: Mon, 08 Oct 2007 19:38:00 -0000 [thread overview]
Message-ID: <470A861E.3080200@portugalmail.pt> (raw)
In-Reply-To: <00a001c809b2$56fc8ec0$04f5ac40$@u-strasbg.fr>
Pierre Muller wrote:
> No, sorry, but the testsuite on cygwin is really a pain,
> it has some signal problems that makes the testsuite
> horribly slow, with tons of timeouts...
> and no I have no easy linux access.
>
I know what you mean ...
I use these patches to be able to test on Cygwin less painfully:
[PATCH] i386_skip_prologue
http://sources.redhat.com/ml/gdb-patches/2006-12/msg00140.html
[[PATCH] Line info in the presence of __main, and NOTE_INSN_FUNCTION_BEG after
scheduling:]
http://gcc.gnu.org/ml/gcc-patches/2006-12/msg00633.html
The gcc patch is really outdated, and doesn't apply to
current gcc svn, so I still have a gcc build from 20061123
to test gdb. Far from ideal, but otherwise, many testcases timeout
and go untested.
I keep wanting to fix this correctly, but I never get around to it.
From the last discussion on the subject, the idea was to teach the
i386 (and any other arch that cares) prologue reader about
__main as a first step. I don't think that's hard.
Cheers,
Pedro Alves
next prev parent reply other threads:[~2007-10-08 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 12:21 Pierre Muller
2007-10-08 13:42 ` Joel Brobecker
2007-10-08 13:51 ` Pierre Muller
2007-10-08 15:02 ` Joel Brobecker
2007-10-08 15:24 ` Pierre Muller
2007-10-08 16:09 ` Daniel Jacobowitz
2007-10-08 16:25 ` Joel Brobecker
2007-10-08 17:18 ` Daniel Jacobowitz
2007-10-08 19:38 ` Pedro Alves [this message]
2007-10-09 14:46 ` Pierre Muller
2007-10-09 16:08 ` 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=470A861E.3080200@portugalmail.pt \
--to=pedro_alves@portugalmail.pt \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--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