Hi, On Sun, Jul 23, 2006 at 12:58:06PM +0200, Hans Leidekker wrote: > On Sunday 23 July 2006 11:26, Jeff Latimer wrote: > > > Interesting. I have not had any problem with them. They also compile > > and run under Windows. Have you got anymore info, a trace? > > It doesn't look very useful to me: > > Unhandled exception: page fault on read access to 0x70697263 in 32-bit code > (0x70697263). > Register dump: > CS:0073 SS:007b DS:007b ES:007b FS:003b GS:0033 > EIP:70697263 ESP:406fd240 EBP:5300000a EFLAGS:00010282( - 00 - RIS1) > EAX:00000001 EBX:20474e49 ECX:5c5c5c5c EDX:405e85bc > ESI:20746f6e EDI:78383025 > Stack dump: > 0x406fd240: 72745374 41676e69 796c616e 53206573 > 0x406fd250: 20627574 756f6873 7220646c 72757465 > 0x406fd260: 5f45206e 49544f4e 204c504d 20746f6e > 0x406fd270: 78383025 5300000a 70697263 72745374 > 0x406fd280: 4f676e69 53207475 20627574 756f6873 > 0x406fd290: 7220646c 72757465 5f45206e 49544f4e
That's all very, very char'ish. 0x70697263 is "pirc", the whole stack is in ASCII range, too (run hexedit on an empty file to verify). Andreas Mohr