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
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
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
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
> > #
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
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
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
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
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
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
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
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
12 matches
Mail list logo