nobody, el 28 de mayo a las 04:08 me escribiste:
> > 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
On Thu, May 28, 2009 at 12:08 AM, nobody 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 ;)
> 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
On Wed, May 27, 2009 at 11:13 PM, nobody 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 sequence
>
>
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 ridicu