From: Benno Schulenberg <bensberg@justemail.net>
To: kerolasa@gmail.com
Cc: "Util-Linux" <util-linux@vger.kernel.org>,
Ondrej Oprala <ooprala@redhat.com>
Subject: Re: hwclock --compare segfaults when run as normal user
Date: Sat, 26 Jul 2014 18:05:09 +0200 [thread overview]
Message-ID: <1406390709.8686.145937949.0F0BF57C@webmail.messagingengine.com> (raw)
In-Reply-To: <CAG27Bk2SkstBkDGR9EiP0UENK1qag0VZ31tLZsjvgCxRss2bpw@mail.gmail.com>
On Sat, Jul 26, 2014, at 16:48, Sami Kerola wrote:
> On 26 July 2014 13:40, Benno Schulenberg <bensberg@justemail.net> wrote:
> > On my system there is no /etc/adjtime file, and then:
> >
> > $ ./hwclock --compare
> > Segmentation fault
>
> I tried to reproduce the issue without success. If you have core file
> could you try to gdb backtrace it?
(gdb) run --compare
Starting program: /home/ben/util-linux-2.25/hwclock --compare
Program received signal SIGSEGV, Segmentation fault.
0x0804cf71 in outb () at /usr/include/sys/io.h:99
99 __asm__ __volatile__ ("outb %b0,%w1": :"a" (__value), "Nd" (__port));
(gdb) bt
#0 0x0804cf71 in outb () at /usr/include/sys/io.h:99
#1 cmos_read () at sys-utils/hwclock-cmos.c:348
#2 atomic () at sys-utils/hwclock-cmos.c:307
#3 hclock_read () at sys-utils/hwclock-cmos.c:456
#4 cmos_clock_busy () at sys-utils/hwclock-cmos.c:472
#5 synchronize_to_clock_tick_cmos () at sys-utils/hwclock-cmos.c:484
#6 0x08049919 in synchronize_to_clock_tick () at sys-utils/hwclock.c:348
#7 0x0804c578 in compare_clock (argc=<value optimized out>, argv=0xbffff414) at sys-utils/hwclock.c:1502
#8 main (argc=<value optimized out>, argv=0xbffff414) at sys-utils/hwclock.c:1941
Benno
--
http://www.fastmail.fm - Choose from over 50 domains or use your own
next prev parent reply other threads:[~2014-07-26 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 12:40 hwclock --compare segfaults when run as normal user Benno Schulenberg
2014-07-26 14:48 ` Sami Kerola
2014-07-26 16:05 ` Benno Schulenberg [this message]
2014-07-28 11:12 ` Karel Zak
2014-07-28 18:50 ` Benno Schulenberg
2014-07-29 6:27 ` Karel Zak
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=1406390709.8686.145937949.0F0BF57C@webmail.messagingengine.com \
--to=bensberg@justemail.net \
--cc=kerolasa@gmail.com \
--cc=ooprala@redhat.com \
--cc=util-linux@vger.kernel.org \
/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