Re: About debugging (again)

2016-10-20 Thread ANtlord via Digitalmars-d-learn

On Monday, 17 October 2016 at 19:17:25 UTC, Basile B. wrote:

On Monday, 17 October 2016 at 19:14:49 UTC, ANtlord wrote:
redirect to ddemangle, that's its job.


Do you know the way how to redirect? I've tried as you have 
written above and this makes impossible to type any command to 
gdb.


Re: About debugging (again)

2016-10-17 Thread Basile B. via Digitalmars-d-learn

On Monday, 17 October 2016 at 19:14:49 UTC, ANtlord wrote:
On Monday, 17 October 2016 at 17:57:19 UTC, Martin Krejcirik 
wrote:

On Monday, 17 October 2016 at 15:45:56 UTC, ANtlord wrote:

GDB 7.7.1


Use latest GDB, 7.10 has got much better D support.


Tested on GDB 7.11.1. Same case :(


redirect to ddemangle, that's its job.


Re: About debugging (again)

2016-10-17 Thread ANtlord via Digitalmars-d-learn

On Monday, 17 October 2016 at 17:53:30 UTC, Basile B. wrote:

On Monday, 17 October 2016 at 17:46:05 UTC, Basile B. wrote:

On Monday, 17 October 2016 at 15:45:56 UTC, ANtlord wrote:

On Monday, 17 October 2016 at 15:43:32 UTC, ANtlord wrote:

[...]


Oh Sorry, I've forgotten about pointing technical parameters.

Ubuntu 14.04
GDB 7.7.1
DMD64 D Compiler v2.071.1


redirect gdb's output to "ddemangle". This is what I do in the 
alpha version of Coedit's GDB commander, now in console mode I 
don't know the exact method.


seems to be:

gdb binary_name | ddemangle


This makes gdb useless. I can't type any command. Propably can I 
use demangle by another way?


Re: About debugging (again)

2016-10-17 Thread ANtlord via Digitalmars-d-learn
On Monday, 17 October 2016 at 17:57:19 UTC, Martin Krejcirik 
wrote:

On Monday, 17 October 2016 at 15:45:56 UTC, ANtlord wrote:

GDB 7.7.1


Use latest GDB, 7.10 has got much better D support.


Tested on GDB 7.11.1. Same case :(


Re: About debugging (again)

2016-10-17 Thread Martin Krejcirik via Digitalmars-d-learn

On Monday, 17 October 2016 at 15:45:56 UTC, ANtlord wrote:

GDB 7.7.1


Use latest GDB, 7.10 has got much better D support.


Re: About debugging (again)

2016-10-17 Thread Basile B. via Digitalmars-d-learn

On Monday, 17 October 2016 at 17:46:05 UTC, Basile B. wrote:

On Monday, 17 October 2016 at 15:45:56 UTC, ANtlord wrote:

On Monday, 17 October 2016 at 15:43:32 UTC, ANtlord wrote:

[...]


Oh Sorry, I've forgotten about pointing technical parameters.

Ubuntu 14.04
GDB 7.7.1
DMD64 D Compiler v2.071.1


redirect gdb's output to "ddemangle". This is what I do in the 
alpha version of Coedit's GDB commander, now in console mode I 
don't know the exact method.


seems to be:

gdb binary_name | ddemangle


Re: About debugging (again)

2016-10-17 Thread Basile B. via Digitalmars-d-learn

On Monday, 17 October 2016 at 15:45:56 UTC, ANtlord wrote:

On Monday, 17 October 2016 at 15:43:32 UTC, ANtlord wrote:
Hello! I've met an issue related to debugging by GDB. Directly 
when I try to show call stack I get like this 
http://pastebin.com/kRFRqznq. How can I make name of methods 
more human readable?


I see part of printed name matches to name of methods from 
code and I can suppose what method was called, but it would be 
great if I can debug application without any supposing.


Sorry if my english is not clear.


Oh Sorry, I've forgotten about pointing technical parameters.

Ubuntu 14.04
GDB 7.7.1
DMD64 D Compiler v2.071.1


redirect gdb's output to "ddemangle". This is what I do in the 
alpha version of Coedit's GDB commander, now in console mode I 
don't know the exact method.




Re: About debugging (again)

2016-10-17 Thread ANtlord via Digitalmars-d-learn

On Monday, 17 October 2016 at 15:43:32 UTC, ANtlord wrote:
Hello! I've met an issue related to debugging by GDB. Directly 
when I try to show call stack I get like this 
http://pastebin.com/kRFRqznq. How can I make name of methods 
more human readable?


I see part of printed name matches to name of methods from code 
and I can suppose what method was called, but it would be great 
if I can debug application without any supposing.


Sorry if my english is not clear.


Oh Sorry, I've forgotten about pointing technical parameters.

Ubuntu 14.04
GDB 7.7.1
DMD64 D Compiler v2.071.1


About debugging (again)

2016-10-17 Thread ANtlord via Digitalmars-d-learn
Hello! I've met an issue related to debugging by GDB. Directly 
when I try to show call stack I get like this 
http://pastebin.com/kRFRqznq. How can I make name of methods more 
human readable?


I see part of printed name matches to name of methods from code 
and I can suppose what method was called, but it would be great 
if I can debug application without any supposing.


Sorry if my english is not clear.