Re: stack trace on linux amd64 ?

2013-06-29 Thread Iain Buclaw
On 29 June 2013 06:42, deadalnix deadal...@gmail.com wrote: On Friday, 28 June 2013 at 20:00:52 UTC, Johannes Pfau wrote: Am Fri, 28 Jun 2013 11:12:25 -0700 schrieb Sean Kelly s...@invisibleduck.org: If I remember correctly, the issue there was that the runtime would need to open the

Re: stack trace on linux amd64 ?

2013-06-28 Thread Sean Kelly
On Jun 24, 2013, at 11:34 AM, Martin Nowak c...@dawg.eu wrote: On 06/24/2013 04:54 PM, deadalnix wrote: Haaa, passing -export-dynamic to the linker did the trick. Exporting symbols from the executable is an ugly solution to get stacktraces. It would be much better if we used the debug

Re: stack trace on linux amd64 ?

2013-06-28 Thread Johannes Pfau
Am Fri, 28 Jun 2013 11:12:25 -0700 schrieb Sean Kelly s...@invisibleduck.org: If I remember correctly, the issue there was that the runtime would need to open the executable or map file and parse it, and it seemed a lot more straightforward to simply make an API call. But if you're inclined

Re: stack trace on linux amd64 ?

2013-06-28 Thread deadalnix
On Friday, 28 June 2013 at 20:00:52 UTC, Johannes Pfau wrote: Am Fri, 28 Jun 2013 11:12:25 -0700 schrieb Sean Kelly s...@invisibleduck.org: If I remember correctly, the issue there was that the runtime would need to open the executable or map file and parse it, and it seemed a lot more

stack trace on linux amd64 ?

2013-06-24 Thread deadalnix
Hi, since I updated dmd 2.063.2, stack traces look like this : object.Exception@libd-llvm/libd/src/util/visitor.d(17): d.ast.type.IdentifierType is not supported. ../bin/sdc() [0x5d3bcf] ../bin/sdc() [0x5ca085] ../bin/sdc() [0x5c9fe3] ../bin/sdc() [0x5d4583] ../bin/sdc()

Re: stack trace on linux amd64 ?

2013-06-24 Thread Dicebot
Do you have -L--export-dynamic in you dmd.conf?

Re: stack trace on linux amd64 ?

2013-06-24 Thread deadalnix
On Monday, 24 June 2013 at 14:37:16 UTC, Dicebot wrote: Do you have -L--export-dynamic in you dmd.conf? Yes, but I'm not linking with dmd (dmd fork itself and don't free any memory, which so I have a huge dead program sitting in memory during all link time). How should I link my stuff to

Re: stack trace on linux amd64 ?

2013-06-24 Thread deadalnix
On Monday, 24 June 2013 at 14:52:29 UTC, deadalnix wrote: On Monday, 24 June 2013 at 14:37:16 UTC, Dicebot wrote: Do you have -L--export-dynamic in you dmd.conf? Yes, but I'm not linking with dmd (dmd fork itself and don't free any memory, which so I have a huge dead program sitting in

Re: stack trace on linux amd64 ?

2013-06-24 Thread Martin Nowak
On 06/24/2013 04:54 PM, deadalnix wrote: Haaa, passing -export-dynamic to the linker did the trick. Exporting symbols from the executable is an ugly solution to get stacktraces. It would be much better if we used the debug information instead. They also provides richer information like line