--- Bernhard Loos <[EMAIL PROTECTED]> wrote:
> I was able to track the problem down, inserting a
> call to
> _my_tls.init_exception_handler
> (_cygtls::handle_exceptions);
> in the function dll::init() solves it. But I'm
> unsure, whether it introduce
> other bugs. If somebody has checked this, I
-Ursprüngliche Nachricht-
Von: Eric Blake
Gesendet: Thu, 30 Mar 2006 15:04:27 + (UTC)
>Bernhard Loos web.de> writes:
>>
>> >You'll have to read the archives. Eric Blake has talked about this very
>> >recently.
>>
>> Sorry, but I'm unable to locate it. The last post mentioning IsBad
Bernhard Loos web.de> writes:
>
> >You'll have to read the archives. Eric Blake has talked about this very
> >recently.
>
> Sorry, but I'm unable to locate it. The last post mentioning IsBad*Ptr
occoured
> arround March 2005 - not very recently.
http://cygwin.com/ml/cygwin/2006-03/msg00455.
> -Ursprüngliche Nachricht-
> Von: Christopher Faylor
> Gesendet: Wed, 29 Mar 2006 19:06:56 -0500
>>>00:00:00.703: LoadLibraryA("H:\cygwin\test\CrashTest\CrashTest.dll") called
>>>from "CYGWIN1.DLL" at address 0x6100FE42 by thread 1.
>>>00:00:00.718: Loaded "CRASHTEST.DLL" at address 0
On Thu, Mar 30, 2006 at 01:35:54AM +0200, Bernhard Loos wrote:
>> -Urspr?ngliche Nachricht-
>> Von: Christopher Faylor
>> Gesendet: Wed, 29 Mar 2006 18:15:34 -0500
>>On Thu, Mar 30, 2006 at 01:10:56AM +0200, Bernhard Loos wrote:
>>>I looked at the problem again this week, but unfortunately
> -Ursprüngliche Nachricht-
> Von: Christopher Faylor
> Gesendet: Wed, 29 Mar 2006 18:15:34 -0500
>On Thu, Mar 30, 2006 at 01:10:56AM +0200, Bernhard Loos wrote:
>>I looked at the problem again this week, but unfortunately I'm unable
>>to debug anything happening after the first SIGSEGV.
On Thu, Mar 30, 2006 at 01:10:56AM +0200, Bernhard Loos wrote:
>I looked at the problem again this week, but unfortunately I'm unable
>to debug anything happening after the first SIGSEGV. I inserted a view
>OutputDebugString()-calls and got those results:
>
>00:00:00.703: LoadLibraryA("H:\cygwin\t
Hello
I looked at the problem again this week, but unfortunately I'm unable to debug
anything happening after the first SIGSEGV.
I inserted a view OutputDebugString()-calls and got those results:
00:00:00.703: LoadLibraryA("H:\cygwin\test\CrashTest\CrashTest.dll") called
from "CYGWIN1.DLL" at ad
On Thu, 2006-03-23 at 06:02 -0800, Gary Zablackis wrote:
> --- skaller <[EMAIL PROTECTED]> wrote:
>
> > On Wed, 2006-03-22 at 03:35 +0100, Bernhard Loos
> > wrote:
> >
> > > If the C++library declares its calls as 'extern
> > "C"' (as it is done in the example),
> > > AFAIK there shouldn't be any
--- skaller <[EMAIL PROTECTED]> wrote:
> On Wed, 2006-03-22 at 03:35 +0100, Bernhard Loos
> wrote:
>
> > If the C++library declares its calls as 'extern
> "C"' (as it is done in the example),
> > AFAIK there shouldn't be any problem.
>
> Doesn't matter what you think you know -- it's not a
> per
On 22 March 2006 22:08, Bernhard Loos wrote:
> It would be really nice, if somebody with some more knowlegde could take a
> look at this,
> because I'm unable to debug the program. I get only some strange
> errormessages and no backtrace.
I did start looking at it with the earlier testcases, a
On Wed, 2006-03-22 at 23:07 +0100, Bernhard Loos wrote:
Code below. I want to confirm: I have two Cygwin installations.
I upgraded one to use 1.5.19, the other uses 1.5.18.
1.5.18 runs the below code fine. It crashes with 1.5.19.
For me even worse -- it crashes even a statically linked
executab
> -Ursprüngliche Nachricht-
> Von: skaller userssourceforgenet>
> On Wed, 2006-03-22 at 03:35 +0100, Bernhard Loos wrote:
>
> > If the C++library declares its calls as 'extern "C"' (as it is done in the
> > example),
> > AFAIK there shouldn't be any problem.
>
> Doesn't matter what you
On Wed, 2006-03-22 at 03:35 +0100, Bernhard Loos wrote:
> If the C++library declares its calls as 'extern "C"' (as it is done in the
> example),
> AFAIK there shouldn't be any problem.
Doesn't matter what you think you know -- it's not a permitted thing
to do, you never know what implementors ar
> -Ursprüngliche Nachricht-
> Von: skaller users sourceforge net>
> Gesendet: 21.03.06 20:31:08
> On Tue, 2006-03-21 at 19:52 +0100, Bernhard Loos wrote:
> > Hello
> >
> > Is there any progress in solving the problem mentioned in this thread:
> > http://cygwin.com/ml/cygwin/2006-03/msg
On Tue, 2006-03-21 at 19:52 +0100, Bernhard Loos wrote:
> Hello
>
> Is there any progress in solving the problem mentioned in this thread:
> http://cygwin.com/ml/cygwin/2006-03/msg00274.html ?
The example in that page is bugged and there is no
reason at all to expect it to work.
The mainline ct.
--- Bernhard Loos <[EMAIL PROTECTED]> wrote:
> Hello
>
> Is there any progress in solving the problem
> mentioned in this thread:
> http://cygwin.com/ml/cygwin/2006-03/msg00274.html ?
>
> Because this is also prevents qt-applications from
> even starting.
>
>
> Bernhard
>
Bernhard,
Hello
Is there any progress in solving the problem mentioned in this thread:
http://cygwin.com/ml/cygwin/2006-03/msg00274.html ?
Because this is also prevents qt-applications from even starting.
Bernhard
__
Verschicken Sie rom
18 matches
Mail list logo
