This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
testsuite/1504: gdb1476.exp needs to recognize "Cannot access memory ..."
- From: mec dot gnu at mindspring dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 10 Jan 2004 11:10:33 -0000
- Subject: testsuite/1504: gdb1476.exp needs to recognize "Cannot access memory ..."
- Reply-to: mec dot gnu at mindspring dot com
>Number: 1504
>Category: testsuite
>Synopsis: gdb1476.exp needs to recognize "Cannot access memory ..."
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unasigned
>State: open
>Class: test-bug
>Submitter-Id: net
>Arrival-Date: Sat Jan 10 11:18:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: mec.gnu@mindspring.com
>Release: gdb HEAD 2004-01-09 22:05:53 UTC
>Organization:
>Environment:
target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0
gdb=HEAD 2004-01-09 22:05:53 UTC
gcc=3.3.2
binutils=2.14
glibc=2.2.93-5-rh
gformat=dwarf-2
glevel=2
>Description:
The 0x0 probe goes like this:
(gdb) x 0
0x0: Cannot access memory at address 0x0
(gdb) UNTESTED: gdb.base/gdb1476.exp: Memory at address 0 is possibly executable
It needs one more pattern.
>How-To-Repeat:
Run gdb1476.exp on native i686-pc-linux-gnu.
Not sensitive to gcc or binutils or debug format.
>Fix:
Add another pattern.
I'm just filing a PR because I need a PR to refer to in my test report if I don't fix it immediately.
>Release-Note:
>Audit-Trail:
>Unformatted: