Re: Problem with .debug info in program

2016-05-24 Thread Kagamin via Digitalmars-d-learn
Probably normal, see this discussion: https://forum.dlang.org/post/mailman.400.1389749305.15871.digitalmar...@puremagic.com Anyway dmd is not known to have a quality backend, try ldc or gdc.

Re: Problem with .debug info in program

2016-05-24 Thread Basile B. via Digitalmars-d-learn
On Tuesday, 24 May 2016 at 13:17:22 UTC, chmike wrote: After closer examination it seam that the second line with 9 is a bogus insertion. Removing it should fix the code line table. app.d 9 0x43aafb app.d 11

Re: Problem with .debug info in program

2016-05-24 Thread chmike via Digitalmars-d-learn
After closer examination it seam that the second line with 9 is a bogus insertion. Removing it should fix the code line table. app.d 90x43aafb app.d 110x43aafe app.d

Problem with .debug info in program

2016-05-24 Thread chmike via Digitalmars-d-learn
Hello, I've notice that gdb was improperly displaying source lines with disassembled code. I looked at the assembly to check what is inlined and what not and the difference between the use of is and == in the machine code. I then tested with objdump with a simple program and saw the same pr

Re: Problem with .debug info in program

2016-05-24 Thread chmike via Digitalmars-d-learn
Here you have the object lines from app with the addresses. ./app.d:[++] app.d 30x43aae8 app.d 50x43aaf0 app.d 70x43aaf7 app.d