I am starting to develop a new air/html/ajax application today and for some reason my trace() output is not being printed to the console window anymore. Plus, I am also not getting any error messages printed for syntax errors or runtime errors. I tried this on a different machine and there was no problem, so it must have been something wrong with this particular machine. I was thinking it had to do with me using the flex 3 sdk, but removing that from my path variable did not help, neither did reinstalling the air sdk. If anyone has encountered this before, help would be greatly appreciated.
This is not specific to the debugger player. The availability of trace statements in the console from ADL is dependent on whether or not any one of the following settings are turned on in your mm.cfg file:
ErrorReportingEnable
TraceOutputFileEnable
Either one of those will block trace output in the console window - stderr I believe - and instead (in the case of TraceOutputFileEnable) redirect it to a log file.
More information about mm.cfg is available here.
I figured it out. It is because I installed the flash debug player. Now the error messages all go the the log file where the debug player writes to.
Related
We are using OPUS Make in our build infrastructure. (Basically traditional make with some wrappers around I guess)
Our codebase is mostly Java and I have been making changes and building for many months now. No issues.
Suddenly, a couple of days back, when I tried to build,i started seeing this error:
OPUS MAKE: Unknown status. Stop.
I see this error no matter what I try to build. More imp - it looks like it is not even trying to actually compile my code and for some reason just stops before with the above error.
I tried doing a clean build. Even manually cleaned up all old generated build files. Still did not work.
I even tried restarting my environment itself. Restarted Clearcase. Still no use.
I see there is a way to build with debug information. Did that also make -d
However, that did not give any useful info either. Just the same line as above. I was hoping that it would give some debug logs or some error code that I could use to solve the problem.
I see there is an option: make -n. That comes out clean. But from the name, it looks like it does not even attempt to run the build itself.
Please suggest what the issue could be.
thx - Om
"Unknown status" means that a shell command in a target returned a status that make did not understand. Run with -d to see which command is failing. And debug that shell command.
I'm using Visual Studio Professional 2013 and I'm doing some very basic windows forms application.
A month ago, I could do everything I wanted without any problem. But I started some new projects today and for absolutely no reasons, I keep getting this error message when I come to debug or compile:
Debug error BC31019 : Unable to write to output file 'path/form.exe System Error &H80070005&
It can happen simply by changing the size of a textbox or modifying the text content in a label... It's very random... And I can even do an undo (ctrl+z) and then I can debug again, but if I try again to do the thing I did that brought the error message, the same message pops again as I try to run.
After reading a little about the subject, I realized that it was because the .exe file became in read-only mode and when I try to remove it, windows wont let me.
The only thing I can do if I really want to continue, is to restart my computer every times it happens. Then I can continue just like normal as my .exe file is no longer in read-only...
I tried tor run a sfc/scannow in my command prompt to see if i had any problems with my frameworks but everything was fine.
Since, it is when i restart my pc that the bug disapears, isn't anything i can do or run somewhere to do the same thing. I need to find why the exe file goes to read-only for nothing and how to get it back to normal without having to restart my pc every time...
Please help me!
thank you
I came across the same issue and it was related to having a command line argument that VS could not find, then when i clicked stop debugging I ended up in this situation as it seemed VS kept a process running.
I could see this process in task manager but could not end it (it started with the same name as my app)
I found closing VS would release this process.
Restarting VS it would then work ok again.
there may be other ways to reproduce the issue but restarting VS seems to release the file and allow you to continue.
I set the exe properties to Read/write. No effect, but when I set app properties/settings to "Always on top" = False the issue went away and is still away.
I'm experiencing a problem that I could not find a solution for yet.
I use Test Complete to automate some GUI related scenarios for an app. I developed some scripts that were working at some point in the past. After a few months I got back and tried to run one of the scripts. The script failed with the following error while it was executing a ClickCell operation on a grid object.
An error occurred.
Possible reasons:
1. The application stopped responding.
2. The application was compiled incorrectly (see the Open Applications topic in the help system).
3. An error occurred in TestComplete.
Technical information:
379 0x80070057 (The parameter is incorrect.) .
Tested object:
...
I executed the same script on another machine with another Test Complete installation and it worked. So I guess it's not the target app that is the problem.
I checked solutions on the web for this issue, but nothing worked. I cleaned up the temp files in all the locations I could find in this answer. The behavior was the same.
So I guess it might be something related with the Test Complete installation. I tried reinstalling it a few times, but it didn't do the trick.
I then used Dependency Walker (as suggested somewhere on the web) on testcomplete.exe and found that there are some dlls that are missing from the Bin directory of Test Complete. Could they generate this error? If yes, how can I get them? As I said, I already re-installed the app a few times.
Did anyone bump into this while working with Test Complete? Is there any .net temp location that I should clean?
We have a .net web application running in fedora 6 under Apache & mono 1.1.18 version. So long it was working good. Suddenly I'm getting the following Server Error in some of the pages,
Server Error in '/' Application
Compilation Error
Description: Error compiling a resource required to service this request. Review your source file and modify it to fix this error.
Error message:
(0,0) : error CS0006: Cannot find assembly `/tmp/apache-temp-aspnet-0/383ed40f/shadow-J7sRQf'
But please note, rest of the pages are loading properly. I know it has something to do with JIT compilation, but why it is happening on some specific pages. Also the error 'Cannot find assembly -----/shadow-J7sRQf' is something suspicious. The same error is displayed across all the browsers all the time.
I have not restarted apache or rebooted the system, as I'm not sure whether this error will occur again and i want to root cause it instead of just ignoring it. i didn't find anything on the httpd log also. I tried to Google it, but was unlucky to find anything specific. Can anyone help me on this? thanks in advance.
Wow, mono 1.1.18 is really old!
If I were you, I would try to stop apache and clean everything in the temporary compilation directory /tmp/apache-temp-aspnet-0/
This should force mono to re-generate everything in this directory.
Then, restart apache and see if it helps.
I am trying to make an embedded Linux for a SuperH processor board. I am using the Buildroot 2012.2 toolchain with uClibc.
All compiles fine but when I try to run some of the BusyBox applets (for instance 'ls' or 'mount'), I get an error like this:
ls: : Unknown error 2
For 'ls' in particular it writes this error number-of-files-in-folder times.
Do you have any ideas what might be causing this? No one on the internet seems to have the same problem and I am crawling the configs for several days without luck.
I believe the error might be caused by misconfigured uClibc but it is just my guess.
Thanks.
EDIT:
I enabled several error message options in uClibc and now I get "no such file or directory" error.
I will answer my own question.
The first and most important problem was, that I have over-optimized uClibc so all reasonable error reports were not included. If you are reading this and have same problem, switch error messages on. They are quite small and very useful.
After resolving human readable error reports, I realized, that the putchar function was disabled. Enabling it solved the problem.
To future generation I advise extreme caution, which features of uClibc you decide to disable, unless you want to spend several days finding an unexpected bug.