This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
external/1568: bigcore.exp fails on i386-linux
- From: drow at sources dot redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 25 Feb 2004 02:24:56 -0000
- Subject: external/1568: bigcore.exp fails on i386-linux
- Reply-to: drow at sources dot redhat dot com
>Number: 1568
>Category: external
>Synopsis: bigcore.exp fails on i386-linux
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: external
>Submitter-Id: net
>Arrival-Date: Wed Feb 25 02:28:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: drow@sources.redhat.com
>Release: HEAD 2004-02-24
>Organization:
>Environment:
i386-linux, kernel version 2.6.3
>Description:
bigcore.exp always generates two FAILs:
FAIL: gdb.base/bigcore.exp: check next heap (address 0x2804a010)
FAIL: gdb.base/bigcore.exp: check prev heap (address 0x3ff4a050)
The corefile says:
6 load3 37fa1000 0804a000 00000000 00002000 2**12
CONTENTS, ALLOC, LOAD, CODE
16 load13 40102000 40200000 00000000 38014000 2**12
CONTENTS, ALLOC, LOAD
17 load14 3fcca000 80321000 00000000 78116000 2**12
CONTENTS, ALLOC, LOAD
GDB says:
(gdb) print $.next
$96 = (struct list *) 0xa0322008
(gdb) print $.next
Cannot access memory at address 0xa0322008
which is in the range of that dumped statement.
This is an upgraded tree. I'll try blowing away and reconfiguring
to see if it's a BFD configury issue.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: