From: Thomas Schwinge <thomas@schwinge.name>
To: svante.signell@telia.com
Cc: gdb-patches@sourceware.org, 579834@bugs.debian.org
Subject: Re: Patch to enable a fully working gdb for GNU/Hurd
Date: Tue, 05 Jul 2011 15:09:00 -0000 [thread overview]
Message-ID: <87liwcg4oi.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <1309876684.3172.144.camel@s1499.it.kth.se>
[-- Attachment #1: Type: text/plain, Size: 2594 bytes --]
Hallo!
On Tue, 05 Jul 2011 16:38:04 +0200, Svante Signell <svante.signell@telia.com> wrote:
> On Mon, 2011-07-04 at 21:17 +0200, Svante Signell wrote:
> > On Mon, 2011-07-04 at 20:18 +0200, Thomas Schwinge wrote:
> > > I think that update_thread_list (which already is exported) should rather
> > > be invoked instead of additionally exporting prune_threads.
> > >
> > > But -- I can no longer reproduce the original problem with GDB HEAD. Can
> > > you?
> >
> > I haven't compiled gdb for some time now. I can take a look, how to get
> > the GDB HEAD? The prune_threads enabled gdb to work properly, and then
> > Samuel applied an earlier version of the patch on debian-ports.
> >
> > Since then the new Debian gdb maintainer wanted to get this patch
> > applied upstream, so I did as was requested. Don't know if it is the
> > correct approach or not. I can try to use update_thread_list instead,
> > once I have the GDB HEAD files.
>
> I have now built gdb HEAD and found that the patch is no longer needed.
OK, and thanks for confirming! Thus, I'll close the GDB PR.
> Additionally adding update_thread_list in gnu_nat.c works for gdb-7.2,
> will propose the following patch to the Debian bug report #579834 in
> case there will be more releases of the 7.2-series until 7.4 is
> released.
Either that, or simply continue to use the patch we're currently using
(no additional work for the Debian maintainers). The existing patch
doesn't do any harm, and can then simply be dropped once Debian is
switching to a GDB release that no longer requires the patch -- which is
still to be determined.
> A few observations when building gdb HEAD: GNU gdb (GDB)
> 7.3.50.20110704-cvs though:
>
> 1) I had to uncomment -Werror when compiling gdb/msg_U.c with Debian
> 4.6.1-1+hurd.1 due to the -Wstrict-aliasing flag set by -Wall, see
> below:
>
> msg_U.c: In function 'msg_del_auth':
> msg_U.c:505:3: error: dereferencing type-punned pointer will break
> strict-aliasing rules [-Werror=strict-aliasing]
This issue is known: search for ``werror'' on
<http://www.bddebian.com/~hurd-web/open_issues/gdb/>.
> 2) When debugging an executable gdb does not find the debugging symbols
> for libraries. For example with libc0.3-dbg installed, the symbols are
> found with 7.2 but not with 7.3.50 when running the built gdb directly
> on an executable having debugging symbols (they are found).
I would guess this is not Hurd-specific, but is due to Debian's multiarch
changes, and is thus a general problem.
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2011-07-05 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 17:14 Svante Signell
2011-07-04 18:34 ` Thomas Schwinge
2011-07-04 19:20 ` Svante Signell
2011-07-04 19:56 ` Joel Brobecker
2011-07-05 14:53 ` Svante Signell
2011-07-05 15:09 ` Thomas Schwinge [this message]
2011-07-05 16:26 ` Tom Tromey
2011-07-05 17:51 ` Svante Signell
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=87liwcg4oi.fsf@kepler.schwinge.homeip.net \
--to=thomas@schwinge.name \
--cc=579834@bugs.debian.org \
--cc=gdb-patches@sourceware.org \
--cc=svante.signell@telia.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