From: Michael Cree <mcree@orcon.net.nz>
To: Richard Henderson <rth@twiddle.net>
Cc: Helge Deller <deller@gmx.de>,
"linux-alpha@vger.kernel.org" <linux-alpha@vger.kernel.org>
Subject: Re: BRSGP relocation truncations in linking kernel for Alpha.
Date: Wed, 26 Oct 2016 19:56:49 +1300 [thread overview]
Message-ID: <20161026065649.2pmhrwx3y35m5fmi@tower> (raw)
In-Reply-To: <249e12e5-5ec7-a7a1-89c5-e3ac52a7ac5d@twiddle.net>
On Tue, Oct 25, 2016 at 11:07:38AM -0700, Richard Henderson wrote:
> On 10/25/2016 01:26 AM, Michael Cree wrote:
> > And while I mention gdb, it no longer works on Alpha since version
> > 7.10. Richard, would you be able to take a look at the bug report:
> > https://sourceware.org/bugzilla/show_bug.cgi?id=19061
>
> In the PR, Pedro has exactly the right pointer to the problem.
>
> >From arch/alpha/kernel/traps.c:
>
> info.si_signo = SIGTRAP;
> info.si_errno = 0;
> info.si_code = TRAP_BRKPT;
> info.si_trapno = 0;
> info.si_addr = (void __user *) regs->pc;
>
> if (ptrace_cancel_bpt(current)) {
> regs->pc -= 4; /* make pc point to former bpt */
> }
>
> So we report the same si_code for executing a breakpoint insn inserted by gdb,
> and a "hardware" breakpoint managed by the kernel. But for the later, we
> already back up the PC.
>
> So gdb winds up backing up the PC twice.
>
> This ought to be fixed by using TRAP_HWBKPT (4) for the ptrace_cancel_bpt case,
> but telling gdb about the issue in gdb/nat/linux-ptrace.c like so:
>
> #elif defined __alpha__
> # define GDB_ARCH_IS_TRAP_BRKPT(X) ((X) == TRAP_BRKPT)
> # define GDB_ARCH_IS_TRAP_HWBKPT(X) ((X) == TRAP_BRKPT || (X) == TRAP_HWBKPT)
>
> which looks confusing, but does get checked:
>
> if (GDB_ARCH_IS_TRAP_BRKPT (siginfo.si_code)
> && GDB_ARCH_IS_TRAP_HWBKPT (siginfo.si_code))
> {
> /* The si_code is ambiguous on this arch -- check debug
> registers. */
> if (!check_stopped_by_watchpoint (lp))
> lp->stop_reason = TARGET_STOPPED_BY_SW_BREAKPOINT;
>
> but at the moment the default definition of GDB_ARCH_IS_TRAP_HWBKPT is always
> false for alpha.
By saying "This ought to be fixed by [...] but at the moment [...]"
are you saying that the fix provided above will not work? Indeed,
it doesn't work: I tried it and just about every test in the gdb test
suite still fails. For example:
Running
/home/mjc/toolchain/gdb-build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.base/break.exp
...
FAIL: gdb.base/break.exp: run until function breakpoint (timeout)
FAIL: gdb.base/break.exp: list marker1 (timeout)
FAIL: gdb.base/break.exp: break lineno (timeout)
FAIL: gdb.base/break.exp: delete $bpnum (timeout)
FAIL: gdb.base/break.exp: run until breakpoint set at a line number
(timeout)
FAIL: gdb.base/break.exp: run until file:function(6) breakpoint
(timeout)
Cheers
Michael.
next prev parent reply other threads:[~2016-10-26 6:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 2:41 BRSGP relocation truncations in linking kernel for Alpha Michael Cree
2016-10-24 20:59 ` Helge Deller
2016-10-25 3:13 ` Richard Henderson
2016-10-25 8:26 ` Michael Cree
2016-10-25 16:58 ` Richard Henderson
2016-10-25 18:07 ` Richard Henderson
2016-10-26 6:56 ` Michael Cree [this message]
2016-10-26 15:18 ` Richard Henderson
2017-02-09 9:58 ` Alpha Kernel Regression [was Re: BRSGP relocation truncations in linking kernel for Alpha.] Michael Cree
2016-10-25 20:01 ` BRSGP relocation truncations in linking kernel for Alpha Thorsten Kranzkowski
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=20161026065649.2pmhrwx3y35m5fmi@tower \
--to=mcree@orcon.net.nz \
--cc=deller@gmx.de \
--cc=linux-alpha@vger.kernel.org \
--cc=rth@twiddle.net \
/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