Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Omair Javaid <omair.javaid@linaro.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] testsuite/gdb.dwarf2: Fix for dw2-dos-drive failure on ARM
Date: Thu, 19 Sep 2013 15:53:00 -0000	[thread overview]
Message-ID: <523B1DDE.2060002@redhat.com> (raw)
In-Reply-To: <CANW4E-3OS0ghsOJim3g=EgZU1sLdcoX8yR1gW0MdTbK20Fsrgw@mail.gmail.com>

Please don't top post.

On 09/19/2013 04:23 PM, Omair Javaid wrote:
> Thanks everyone for the feedback.
> 
> I am getting following problem with 1byte text section in the dw2-dos-drive.exp
> 
> (gdb) PASS: gdb.dwarf2/dw2-dos-drive.exp: set breakpoint pending off
> break 'z:file.c':func
> Cannot access memory at address 0x0
> 
> When I change this to 4bytes the problem gets fixed. That is why I
> thought this could be an unaligned illegal memory access but I accept
> that the above comments verify that its not a alignment issue.
> 
> Can anyone help me figure out what could be the cause of this problem?

Breakpoint instructions on ARM are 4-byte wide.  It sounds like
GDB is trying to read the memory at the breakpoint's address, and
that fails (that error message comes from GDB, not the program).
AFAICS, the test doesn't execute the compiled object's code, so
GDB will try to read memory from the binary's sections.  As the
section is only 1 byte long, and probably no other section is allocated
contiguously, that'll fail...  To confirm, debug GDB under GDB,
and put a break on throw_it or some such.  Then work up the stack
to see where that is thrown, and why.

-- 
Pedro Alves


  reply	other threads:[~2013-09-19 15:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANW4E-3h4UODqrXEjP2Z8AmZa+eYtXnTY337EosXTSE6016uGQ@mail.gmail.com>
2013-07-15 10:27 ` Omair Javaid
2013-07-30 15:38   ` Pedro Alves
2013-09-19 15:23     ` Omair Javaid
2013-09-19 15:53       ` Pedro Alves [this message]
2013-10-01  8:32         ` Omair Javaid
2013-10-01 15:34           ` Pedro Alves
2013-12-02 21:17             ` Omair Javaid
2014-01-15 18:39               ` Omair Javaid
2014-01-16 10:25               ` Pedro Alves
2014-01-16 10:35                 ` Omair Javaid
2014-01-16 10:58                   ` Pedro Alves

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=523B1DDE.2060002@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=omair.javaid@linaro.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