MCS is Crashing

[HenrikOlsson]

NTDLL.DLL is a windows system file containing library data for the core windows kernel. This would suggest that the issue is more likely a conflict between it and other system files rather than MSC itself crashing

If it's conflict between ntdll.dll and other system files then why is MCS the only program crashing with that particular error message? Do you believe MCS is the only program using a particular function exported by ntdll.dll?

MCS is the only program I've seen do this and it's done it to me hundreds of times on 3 different computers, it's done it to many other users as well yet the notion that it's got nothing to do with MCS keeps comming back.

The enduser (me) doesn't really care if the actual error is in the MCS source or in any of the supporting files MCS is using, it's MCS that crashes. If it does that due to a bug in MCS code itself or the way it calls some library function or an actual bug IN that library it ought to be in the developers interest to fix it but but he's already got my money and doesn't seem to care that much despite multiple threads and reports for YEARS. And MeLabs claims they can't do anything about it since they're not the developers, handy isn't it?

[richard]

And MeLabs claims they can't do anything about it since they're not the developers

they however could have spent some resources getting mplabx integration sorted , with proper language syntax plugin and source level
debugging .
I would have paid twice the 3.1 upgrade price just for that, there is little point in supporting newer chips when common "command line"
programmers can't program them . also the new chips with pin select modules can't take advantage of the "microchip code configurator "
without mplabx

still dreaming

[HenrikOlsson]

Indeed, so would I.

They tout PBP as a professional-level development tool and I can't really say anything bad about the compiler itself but the supporting / surounding stuff does leave a lot to desire. We're way past writing programs in Notepad, compiling from the commandline, loading the hex file into MPLAB and programming with the PICStart+

Proper and seamless integration into MPLABX is what's needed for the advanced users. After seeing Charles video a month or so ago I was able to compile a program within MPLAB but wasn't even able to set a breakpoint.

[richard]

you need to go back to mplabx 2.35 or earlier for breakpoints to be placed easily, but then I can't use my 16f1619