Well, as I wrote initially, "It fixes one possible source of the SIGABRT problem". Knowing that this happens when the machine is rebooted is useful. Is there anything in the system logs that might be relevant, such as "process xy doesn't respond, sending ABORT signal"?
@Bernd: Is there hope, that the performance problem for AMD/Win systems gets fixed?
It definitely will. However my first quick shots addressing this (e.g. compiling the relevant code for Windows with the same compiler I used for Linux) didn't yield anything useful (i.e. linking in the above example) yet. I'll continue to work on this.
Well, as I wrote initially,
)
Well, as I wrote initially, "It fixes one possible source of the SIGABRT problem". Knowing that this happens when the machine is rebooted is useful. Is there anything in the system logs that might be relevant, such as "process xy doesn't respond, sending ABORT signal"?
BM
BM
RE: @Bernd: Is there hope,
)
It definitely will. However my first quick shots addressing this (e.g. compiling the relevant code for Windows with the same compiler I used for Linux) didn't yield anything useful (i.e. linking in the above example) yet. I'll continue to work on this.
BM
BM
See here. BM
)
See here.
BM
BM