On 06/14/12 18:38, Vlad Khorsun wrote:
>> Is it enough to agree that keeping warnings in our API is the only
>> correct solution?
> I, personally, prefer to have warnings, but, probably it should be
> delivered not using status-vector. If we can produce and deliver many
> warnings per stateme
On 14/06/2012 09:23, Mark Rotteveel wrote:
> On 14-6-2012 12:50, Adriano dos Santos Fernandes wrote:
>> On 14/06/2012 06:13, Alex Peshkoff wrote:
>>> For me this looks like regression, sorry.
>>>
>> If you talking about specific subject about warning removal, I'd instead
>> call it "let bad legacy
I'm only setup (sort of) to get stack traces in my test environment, not
production. All I have to offer is the following from the windows event log:
Faulting application fbserver.exe, version 2.1.5.18479, time stamp 0x4f73e2ed,
faulting module fbserver.exe, version 2.1.5.18479, time stamp 0x4f7
<>
http://www.ibphoenix.com/resources/documents/development/doc_35
Please read.
Regards
Paul
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has ch
-- Original Message ---
From: "Paul Beach"
> http://www.ibphoenix.com/resources/documents/development/doc_35
--- End of Original Message ---
I've also (just now) followed the instructions at
http://msdn.microsoft.com/en-us/library/windows/desktop/bb787181(v=vs.85).aspx
