From: Bob Tracy <rct@frus.com>
To: Witold Baryluk <witold.baryluk@gmail.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
debian-alpha@lists.debian.org, linux-alpha@vger.kernel.org
Subject: Re: dbus-daemon unaligned accesses
Date: Sat, 18 Jan 2020 23:49:16 -0600 [thread overview]
Message-ID: <20200119054916.GA7215@gherkin.frus.com> (raw)
In-Reply-To: <CAEGMnwooY_KiNzdwUMnQ2k6GyK8884BYAw0-HjrdJGtbnz2PgA@mail.gmail.com>
On Sat, Jan 18, 2020 at 05:33:31PM +0000, Witold Baryluk wrote:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932381
At first glance, that certainly appears to be the issue. The
conversation seems to have stalled-out as of July 2019.
memcpy() looks to be a good way of handling the problem, for the
reasons mentioned. Did you try that fix? If so, did it work for you?
--Bob
next prev parent reply other threads:[~2020-01-19 5:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 16:06 dbus-daemon unaligned accesses Bob Tracy
2020-01-18 16:36 ` John Paul Adrian Glaubitz
2020-01-18 17:33 ` Witold Baryluk
2020-01-19 5:49 ` Bob Tracy [this message]
2020-01-19 15:02 ` Witold Baryluk
2020-01-19 22:42 ` Witold Baryluk
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=20200119054916.GA7215@gherkin.frus.com \
--to=rct@frus.com \
--cc=debian-alpha@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-alpha@vger.kernel.org \
--cc=witold.baryluk@gmail.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