Viktor Szakáts wrote:
>
>> Any clues?
>
> To me it looks like a regular problem, not
> some kind of bug.
>
> If you think hbmk2 is the suspicious piece one here,
> simply try the harbour cmdline (printed by -trace) directly.
>
No, it is not hbMK2 bug at all.
It is Harbour compiler's bug which starts dumping warnings
after a certain limit of confronted warnings are reached.
It can be illustrated like this:
(code - sephagatti - compilable with minimum warning level )
a.prg -> 20000 lines code; 11000 warnings - compiles fine
b.prg -> 15000 lines code; 7000 warnings - compiles fine
c.prg -> 27000 lines code; 13000 warnings - misbehave - warnings are dumped
to console
and at the end process aborted.
Keep on shuffling the order of prgs or add few small ones inbetween
the dump appears at other file.
Przemek, can you please look into this issue?
> If it behaves differently, it's a HB_COMPILE() function
> problem, if not, look closer into Clipper/Harbour behavior
> to find out why it's behaving like it does.
>
> Another possibility is some Clipper incompatible behavior
> of xhb which masked some problems in your code thus far.
>
If I issue the same command copied from hbIDE log direct on command line,
I get the same warning dump and process aborts.
> I maintain it's not a hbmk2 problem.
>
Me too.
BTW, one thought, I can see hb_threadStart() in hbMK2,
can I deactivate it any way to see if it improves or alters the results?
I have seen something which might belong to this, but reveal
later once I am sure it is the default.
-----
enjoy hbIDEing...
Pritpal Bedi
http://hbide.vouch.info/
--
View this message in context:
http://harbour-devel.1590103.n2.nabble.com/hbMK2-xhb-issues-switch-n-by-default-which-breaks-process-tp5005754p5016412.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
