Re: D and GDB

2017-06-05 Thread H. S. Teoh via Digitalmars-d-learn
On Mon, Jun 05, 2017 at 05:34:14AM +, Basile B. via Digitalmars-d-learn wrote: > On Monday, 5 June 2017 at 01:07:51 UTC, H. S. Teoh wrote: > > > > It can't be any more trivial than just running ddemangle, which is > > found in the dlang/tools repo on github. [...] > > (Arguably this should be

Re: D and GDB

2017-06-05 Thread Mike Wey via Digitalmars-d-learn
On 06/05/2017 03:07 AM, H. S. Teoh via Digitalmars-d-learn wrote: It can't be any more trivial than just running ddemangle, which is found in the dlang/tools repo on github. (Arguably this should be shipped by default with dmd... or is it already?) Recent? versions of gdb also support demangli

Re: D and GDB

2017-06-04 Thread Basile B. via Digitalmars-d-learn
On Monday, 5 June 2017 at 01:07:51 UTC, H. S. Teoh wrote: It can't be any more trivial than just running ddemangle, which is found in the dlang/tools repo on github. Trivial i don't know but i had the feeling that the OP complained about the stack trace not being readable although all the an

Re: D and GDB

2017-06-04 Thread H. S. Teoh via Digitalmars-d-learn
On Sun, Jun 04, 2017 at 07:24:17PM +, Basile B. via Digitalmars-d-learn wrote: [...] > you have to pipe the output to ddemangle. Here's the output: > > #0  0x7fffc770 in ?? () > > #1  0x77bb3d80 in dvb_scan_transponder () from > > /usr/lib/x86_64-linux-gnu/libdvbv5.so.0 > > #

Re: D and GDB

2017-06-04 Thread Stefan Koch via Digitalmars-d-learn
On Sunday, 4 June 2017 at 18:13:41 UTC, Russel Winder wrote: On Sun, 2017-06-04 at 20:31 +0300, ketmar via Digitalmars-d-learn wrote: [...] Sadly even using the correct command, I am not getting any data that helps infer what the is going on. :-( [...] My guess is a null pointer :) c

Re: D and GDB

2017-06-04 Thread Jacob Carlborg via Digitalmars-d-learn
On 2017-06-04 20:13, Russel Winder via Digitalmars-d-learn wrote: On Sun, 2017-06-04 at 20:31 +0300, ketmar via Digitalmars-d-learn wrote: maybe 'cause backtrace is called with `bt` command? ;-) Sadly even using the correct command, I am not getting any data that helps infer what the is

Re: D and GDB

2017-06-04 Thread Paolo Invernizzi via Digitalmars-d-learn
On Sunday, 4 June 2017 at 19:24:17 UTC, Basile B. wrote: On Sunday, 4 June 2017 at 18:13:41 UTC, Russel Winder wrote: [...] you have to pipe the output to ddemangle. Personally i don't know how to do this by hand since my IDE does the task automatically (http://bbasile.github.io/Coedit/widg

Re: D and GDB

2017-06-04 Thread Basile B. via Digitalmars-d-learn
On Sunday, 4 June 2017 at 18:13:41 UTC, Russel Winder wrote: Sadly even using the correct command, I am not getting any data that helps infer what the is going on. :-( #0  0x7fffc770 in ?? () #1  0x77bb3d80 in dvb_scan_transponder () from /usr/lib/x86_64-linux-gnu/libdvbv

Re: D and GDB

2017-06-04 Thread Russel Winder via Digitalmars-d-learn
On Sun, 2017-06-04 at 20:31 +0300, ketmar via Digitalmars-d-learn wrote: > > > maybe 'cause backtrace is called with `bt` command? ;-) Sadly even using the correct command, I am not getting any data that helps infer what the is going on. :-( #0  0x7fffc770 in ?? () #1  0x7

Re: D and GDB

2017-06-04 Thread Russel Winder via Digitalmars-d-learn
On Sun, 2017-06-04 at 20:31 +0300, ketmar via Digitalmars-d-learn wrote: > […] > maybe 'cause backtrace is called with `bt` command? ;-) :-) Well it is 14 years since I started a gdb instance. -- Russel. = Dr Russel Wi

Re: D and GDB

2017-06-04 Thread ketmar via Digitalmars-d-learn
Russel Winder wrote: I thought I had left SIGSEGV debugging behind, but it seems not. However whilst the C++/CLion debug tooling is excellent, D seems to be without. I guess there must be some gdb magic I am missing, but: Program received signal SIGSEGV, Segmentation fault. 0x7fffc788

D and GDB

2017-06-04 Thread Russel Winder via Digitalmars-d-learn
I thought I had left SIGSEGV debugging behind, but it seems not. However whilst the C++/CLion debug tooling is excellent, D seems to be without. I guess there must be some gdb magic I am missing, but: Program received signal SIGSEGV, Segmentation fault. 0x7fffc788 in ?? () gdb>b Breakpoin