| Reporter's email: |
mec@shout.net |
CC these people
on PR status email: |
|
| |
|
| Number: |
1377
|
| Category: |
c++
|
| Synopsis: |
[regression] g++ 2.95.3, dwarf-2, hand function call: SIGSEGV
|
| Confidential: |
no
|
| Severity: |
serious
|
| Priority: |
medium
|
| Responsible: |
chastain
|
| State: |
closed
|
| Class: |
sw-bug
|
| Submitter-Id: |
net
|
| Arrival-Date: |
Sun Sep 14 22:58:01 UTC 2003
|
| Closed-Date: |
Fri Dec 05 05:00:18 UTC 2003
|
| Last-Modified: |
Fri Dec 05 05:00:18 UTC 2003
|
| Originator: |
mec@shout.net
|
| Release: |
gdb HEAD 2003-09-13 14:00:00 UTC
|
| Organization: |
|
| Environment: |
target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0
gdb=HEAD 2003-09-13 14:00:00 UTC
gcc=2.95.3
binutils=2.14
glibc=2.2.93-5-rh
gformat=dwarf-2
glevel=2
|
| Description: |
gdb coughs up in virtfunc.exp:
(gdb) PASS: gdb.cp/virtfunc.exp: print pDd->vg()
print pEe->vvb()^M
^M
Program received signal SIGSEGV, Segmentation fault.^M
0x00000000 in ?? ()^M
The program being debugged was signaled while in a function called from GDB.^M
GDB remains in the frame where the signal was received.^M
To change this behavior use "set unwindonsignal on"^M
Evaluation of the expression containing the function (at 0x0) will be abandoned.
^M
(gdb) FAIL: gdb.cp/virtfunc.exp: print pEe->vvb()
gdb regressed some time between 2003-09-11 07:16:02 UTC and 2003-09-13 14:00:00 UTC.
My executable file is attached.
|
| File Attachments: |
|
| How-To-Repeat: |
gdb namespace
(gdb) break test_calls
(gdb) run
(gdb) print pAe->f()
$2 = 20
(gdb) print pAa->f()
$3 = 1
(gdb) print pDe->vg()
$4 = 202
(gdb) print pADe->vg()
$5 = 202
(gdb) print pDd->vg()
$6 = 101
(gdb) print pEe->vvb()
Or, just run virtfunc.exp and look at these particular tests.
|
| Fix: |
|
| Release-Note: |
|
| Unformatted: |
|