From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jan.kratochvil@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] workaround gcc46: prologue skip skips too far (PR 12435) #2
Date: Sun, 24 Jul 2011 18:16:00 -0000 [thread overview]
Message-ID: <201107241803.p6OI3rMR008990@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20110722215821.GA3433@host1.jankratochvil.net> (message from Jan Kratochvil on Fri, 22 Jul 2011 23:58:21 +0200)
> Date: Fri, 22 Jul 2011 23:58:21 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Hi,
>
> this is an improved patch of a former:
> [patch] workaround gcc46: prologue skip skips too far (PR 12435)
> http://sourceware.org/ml/gdb-patches/2011-03/msg01108.html
> cancel/FYI: Re: [patch] workaround gcc46: prologue skip skips too far (PR 12435)
> http://sourceware.org/ml/gdb-patches/2011-03/msg01123.html
>
> For example `break error' does not work for debugging GDB with gcc-4.6.x.
>
> As gcc-4.6.0 and now even 4.6.1 still has this bug and I have seen a user(s?)
> on non-Fedora platform asking about this bug and as there may be enough
> binaries out there (although it affects only -O0 -g compilation) coded it
> properly I have coded the workaround properly this time.
>
> It does not solve overlays well, but the code just does not work for
> overlays, it has no other negative effect.
Sorry, but what do you mean with "overlays" here?
next prev parent reply other threads:[~2011-07-24 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 23:04 Jan Kratochvil
2011-07-24 18:16 ` Mark Kettenis [this message]
2011-07-24 20:00 ` Jan Kratochvil
2011-09-08 15:54 ` Jan Kratochvil
2011-09-08 17:31 ` Doug Evans
2011-09-08 19:13 ` Jan Kratochvil
2011-09-09 19:52 ` Jan Kratochvil
2011-09-12 17:23 ` Doug Evans
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=201107241803.p6OI3rMR008990@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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