This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/19424] New: frequent core dump
- From: "faorg-lists at yahoo dot co.uk" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 04 Jan 2016 15:01:48 +0000
- Subject: [Bug gdb/19424] New: frequent core dump
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=19424
Bug ID: 19424
Summary: frequent core dump
Product: gdb
Version: 7.10
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: faorg-lists at yahoo dot co.uk
Target Milestone: ---
gdb process terminated with a core dump.
Closing this gdb session.
I haven't been able to identify the steps to reproduce, but it happens
frequently debugging a cpp program linked against Fortran libs (gcc 4.8.3,
Intel ifort 13.0.1 20121010).
The core file contains this:
#0 0x0000003519035617 in raise () from /lib64/libc.so.6
#1 0x0000003519036d08 in abort () from /lib64/libc.so.6
#2 0x0000000000694136 in dump_core () at utils.c:560
#3 0x0000000000696425 in internal_vproblem (problem=problem@entry=0xa43ea0
<internal_error_problem>, file=<optimized out>, line=<optimized out>,
fmt=<optimized out>, ap=ap@entry=0x7fff18d5ddb8) at utils.c:768
#4 0x00000000006964f9 in internal_verror (file=<optimized out>,
line=<optimized out>, fmt=<optimized out>, ap=ap@entry=0x7fff18d5ddb8) at
utils.c:794
#5 0x00000000006c8af2 in internal_error (file=file@entry=0x7b05d0
"linux-nat.c", line=line@entry=3178, fmt=<optimized out>) at
./common/errors.c:55
#6 0x00000000004b0871 in linux_nat_filter_event (status=9, lwpid=<optimized
out>) at linux-nat.c:3178
#7 linux_nat_wait_1 (ops=<optimized out>, target_options=1,
ourstatus=0x7fff18d5e1e0, ptid=...) at linux-nat.c:3489
#8 linux_nat_wait (ops=<optimized out>, ptid=..., ourstatus=0x7fff18d5e1e0,
target_options=1) at linux-nat.c:3752
#9 0x00000000004b56a7 in thread_db_wait (ops=<optimized out>, ptid=...,
ourstatus=0x7fff18d5e1e0, options=1) at linux-thread-db.c:1508
#10 0x00000000005ea1ae in delegate_wait (self=<optimized out>, arg1=...,
arg2=<optimized out>, arg3=<optimized out>) at target-delegates.c:116
#11 0x00000000005f82a5 in target_wait (ptid=..., status=<optimized out>,
options=<optimized out>) at target.c:2229
#12 0x00000000005b741d in fetch_inferior_event
(client_data=client_data@entry=0x0) at infrun.c:3303
#13 0x00000000005cdafc in inferior_event_handler (event_type=INF_REG_EVENT,
client_data=0x0) at inf-loop.c:56
#14 0x00000000005cbf3d in gdb_wait_for_event (block=block@entry=0) at
event-loop.c:834
#15 0x00000000005cc150 in gdb_do_one_event () at event-loop.c:298
#16 0x00000000005cc1fe in start_event_loop () at event-loop.c:347
#17 0x00000000005c5e43 in captured_command_loop (data=data@entry=0x0) at
main.c:318
#18 0x00000000005c2e4d in catch_errors (func=func@entry=0x5c5e30
<captured_command_loop>, func_args=func_args@entry=0x0,
errstring=errstring@entry=0x7ae96d "", mask=mask@entry=RETURN_MASK_ALL) at
exceptions.c:240
#19 0x00000000005c6dde in captured_main (data=data@entry=0x7fff18d5e530) at
main.c:1157
#20 0x00000000005c2e4d in catch_errors (func=func@entry=0x5c6370
<captured_main>, func_args=func_args@entry=0x7fff18d5e530,
errstring=errstring@entry=0x7ae96d "", mask=mask@entry=RETURN_MASK_ALL) at
exceptions.c:240
#21 0x00000000005c728b in gdb_main (args=args@entry=0x7fff18d5e530) at
main.c:1165
#22 0x0000000000466765 in main (argc=<optimized out>, argv=<optimized out>) at
gdb.c:32
Running on Linux version 3.14.4-100.fc19.x86_64. gdb 7.10 compiled from your
source. I have had similar problems with several older versions.
--
You are receiving this mail because:
You are on the CC list for the bug.