Illegal Instruction
Russel Winder
russel at winder.org.uk
Tue Nov 7 16:54:50 UTC 2017
David,
> What is the failing instruction (use gdb)? How can we reproduce the
> issue?
To date gdb has failed me, but this is most certainly because I am
effectively a newbie at using gdb. What I can show is:
(gdb) r
Starting program: /home/users/russel/BuildArea/Me-TV_D/me-tv
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe7c15700 (LWP 22993)]
[New Thread 0x7fffe7414700 (LWP 22994)]
[New Thread 0x7fffe50f4700 (LWP 22995)]
[New Thread 0x7fffe48f3700 (LWP 22996)]
[New Thread 0x7fffd7fff700 (LWP 22997)]
Control window daemon going into receive.
Thread 4 "me-tv" received signal SIGUSR1, User defined signal 1.
[Switching to Thread 0x7fffe50f4700 (LWP 22995)]
pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
185 ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or directory.
(gdb) bt
#0 0x00007ffff54b315f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1 0x00007ffff595fc90 in core.sync.condition.Condition.wait() () at /usr/lib/x86_64-linux-gnu/libdruntime-ldc.so.74
#2 0x00005555555ee9bf in std.concurrency.MessageBox.get!(void(frontend_manager.FrontendAppeared) @safe function, void(frontend_manager.AdapterDisappeared) @safe function, void(frontend_manager.FrontendDisappeared) @safe function, void(std.concurrency.OwnerTerminated) @safe delegate).get(scope void(frontend_manager.FrontendAppeared) @safe function, scope void(frontend_manager.AdapterDisappeared) @safe function, scope void(frontend_manager.FrontendDisappeared) @safe function, scope void(std.concurrency.OwnerTerminated) @safe delegate) ()
#3 0x00005555555ed529 in control_window.runControlWindowDaemon() ()
#4 0x00007ffff596199a in thread_entryPoint () at /usr/lib/x86_64-linux-gnu/libdruntime-ldc.so.74
#5 0x00007ffff54ad494 in start_thread (arg=0x7fffe50f4700) at pthread_create.c:333
#6 0x00007ffff4eedabf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
(gdb)
The problem of reproducibility has been challenging me for a day as
what's the point of a bug report without a bug to be shown. I guess
this is why I arrived here first. I have no clue what to drag out of my
code as a small exemplar of the problem, and I am sure no-one wants to
work with my code.
> SIGILL can be due to hitting an assert(0) or similarly unreachable
> code
> (LLVM emits ud2 as a trap instruction), or due to genuine
> instructions
> not supported on the target (e.g. AVX2, etc.).
In case of doubt about it being an illegal instruction, which it may
not be but, when run out of gdb:
Control window daemon going into receive.
/dev/dvb/adapter0/frontend0 being added.
Illegal instruction
I think what I am really asking here is to be given guidance providing
the data that will be helpful to people.
--
Russel.
==========================================
Dr Russel Winder t: +44 20 7585 2200
41 Buckmaster Road m: +44 7770 465 077
London SW11 1EN, UK w: www.russel.org.uk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.puremagic.com/pipermail/digitalmars-d-ldc/attachments/20171107/78664e66/attachment.sig>
More information about the digitalmars-d-ldc
mailing list