Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 578194 - sys-devel/gdb 7.10.1 and 7.11 process record problems
Summary: sys-devel/gdb 7.10.1 and 7.11 process record problems
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-24 16:33 UTC by Juraj Variny
Modified: 2019-12-29 11:37 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (einfo20160324.txt,6.85 KB, text/plain)
2016-03-24 16:33 UTC, Juraj Variny
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Juraj Variny 2016-03-24 16:33:14 UTC
Created attachment 428944 [details]
emerge --info

It works with simple singlethreaded programs, but not with certain multithreaded app, I have not yet determined whether threads or something else causes the problem.

On x64 system, AMD Athlon II 630 CPU.

================== With gdb-7.10.1:
^C
Program received signal SIGINT, Interrupt.
0x00000034df6e152d in poll () at ../sysdeps/unix/syscall-template.S:81
81      ../sysdeps/unix/syscall-template.S: File not found.
(gdb) record
(gdb) c
Continuing.
(null)Process record: failed to record execution log.

[Thread 0x7fffc05e4740 (LWP 5031)] #1 stopped.


================== With gdb-7.11:
^C
Thread 1 "euclient" received signal SIGINT, Interrupt.
0x00000034df6e152d in poll () at ../sysdeps/unix/syscall-template.S:81
81      ../sysdeps/unix/syscall-template.S: File not found.
(gdb) record
(gdb) c
Continuing.
./nat/x86-linux-dregs.c:146: internal-error: x86_linux_update_debug_registers: Assertion `lwp_is_stopped (lwp)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

This is a bug, please report it.  For instructions, see:
<https://bugs.gentoo.org/>.

zsh: abort (core dumped)  gdb -x ../gdbinit

================= Backtrace from above core:

#0  0x00000034df633717 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#1  0x00000034df634b3d in __GI_abort () at abort.c:89
#2  0x00000000006ab616 in dump_core () at utils.c:561
#3  0x00000000006added in internal_vproblem (problem=problem@entry=0xc40a20 <internal_error_problem>, file=<optimized out>, line=<optimized out>, fmt=<optimized out>, ap=ap@entry=0x7ffede87ce10) at utils.c:769
#4  0x00000000006adeb9 in internal_verror (file=<optimized out>, line=<optimized out>, fmt=<optimized out>, ap=ap@entry=0x7ffede87ce10) at utils.c:795
#5  0x00000000006e224f in internal_error (file=file@entry=0x7b8258 "./nat/x86-linux-dregs.c", line=line@entry=146, fmt=<optimized out>) at ./common/errors.c:55
#6  0x00000000004b1748 in x86_linux_update_debug_registers (lwp=0xf652c50) at ./nat/x86-linux-dregs.c:146
#7  0x00000000004a058c in linux_resume_one_lwp_throw (lp=lp@entry=0xf652c50, step=step@entry=1, signo=signo@entry=GDB_SIGNAL_0) at linux-nat.c:1421
#8  0x00000000004a1d3a in linux_resume_one_lwp (lp=lp@entry=0xf652c50, step=step@entry=1, signo=signo@entry=GDB_SIGNAL_0) at linux-nat.c:1475
#9  0x00000000004a4b8a in linux_nat_resume (ops=<optimized out>, ptid=..., step=1, signo=GDB_SIGNAL_0) at linux-nat.c:1666
#10 0x00000000006cea2e in record_full_wait_1 (options=1, status=0x7ffede87d2c0, ptid=..., ops=0xc62580 <record_full_ops>) at record-full.c:1181
#11 record_full_wait (ops=0xc62580 <record_full_ops>, ptid=..., status=0x7ffede87d2c0, options=1) at record-full.c:1354
#12 0x00000000005f7add in delegate_wait (self=<optimized out>, arg1=..., arg2=<optimized out>, arg3=<optimized out>) at target-delegates.c:116
#13 0x0000000000607da4 in target_wait (ptid=..., status=status@entry=0x7ffede87d2c0, options=options@entry=1) at target.c:2258
#14 0x00000000005b4e59 in do_target_wait (ptid=..., status=status@entry=0x7ffede87d2c0, options=1) at infrun.c:3642
#15 0x00000000005c0d97 in fetch_inferior_event (client_data=<optimized out>) at infrun.c:3900
#16 0x00000000005d995a in inferior_event_handler (event_type=<optimized out>, client_data=<optimized out>) at inf-loop.c:44
#17 0x00000000005d7cc4 in check_async_event_handlers () at event-loop.c:1038
#18 gdb_do_one_event () at event-loop.c:302
#19 0x00000000005d7d8e in start_event_loop () at event-loop.c:347
#20 0x00000000005d1533 in captured_command_loop (data=data@entry=0x0) at main.c:318
#21 0x00000000005ce055 in catch_errors (func=func@entry=0x5d1520 <captured_command_loop>, func_args=func_args@entry=0x0, errstring=errstring@entry=0x7b8a99 "", mask=mask@entry=RETURN_MASK_ALL) at exceptions.c:240
#22 0x00000000005d2656 in captured_main (data=data@entry=0x7ffede87d600) at main.c:1157
#23 0x00000000005ce055 in catch_errors (func=func@entry=0x5d1b80 <captured_main>, func_args=func_args@entry=0x7ffede87d600, errstring=errstring@entry=0x7b8a99 "", mask=mask@entry=RETURN_MASK_ALL) at exceptions.c:240
#24 0x00000000005d2afb in gdb_main (args=args@entry=0x7ffede87d600) at main.c:1165
#25 0x000000000045d735 in main (argc=<optimized out>, argv=<optimized out>) at gdb.c:32
Comment 1 XMs 2018-04-16 06:33:54 UTC
I have this issue with gdb-7.12.1, too
Comment 2 Sergei Trofimovich (RETIRED) gentoo-dev 2019-11-12 00:05:29 UTC
Does it still happen for people on modern gdb?