how to find stack trace of Error: 4invalid UTF-8 sequence Error: std.format int argument expected?

2009-05-27 Thread nobody
dmd v1.045 on Linux, I got error like: Error: 4invalid UTF-8 sequence Error: std.format int argument expected Then I run the program under debugger, there is no indication where the error occurred: Error: 4invalid UTF-8 sequence Program exited with code 01. (gdb) where No stack. This is

Re: how to find stack trace of Error: 4invalid UTF-8 sequence Error: std.format int argument expected?

2009-05-27 Thread Jarrett Billingsley
On Wed, May 27, 2009 at 11:13 PM, nobody n...@where.com wrote: dmd v1.045 on Linux, I got error like: Error: 4invalid UTF-8 sequence Error: std.format int argument expected Then I run the program under debugger, there is no indication where the error occurred: Error: 4invalid UTF-8

Re: how to find stack trace of Error: 4invalid UTF-8 sequence Error: std.format int argument expected?

2009-05-27 Thread nobody
From what I understand, you can set GDB to break whenever _d_throw is called. I don't know the syntax. Thanks for the hint. I googled it, here's the way to do it: $ objdump -x your.exe | grep throw 0819c1e0 g F .text 0217 _d_th...@4 (gdb) break *0x0819c1e0 Breakpoint 1

Re: how to find stack trace of Error: 4invalid UTF-8 sequence Error: std.format int argument expected?

2009-05-27 Thread Jarrett Billingsley
On Thu, May 28, 2009 at 12:08 AM, nobody n...@where.com wrote: If you don't want to use a debugger, there's always printf/writefln/Stdout debugging. using writefln to find writefln errors? ;-) As long as you don't use invalid UTF-8 data in your debugging statements ;)