I edited this question, as now it seems it's not a coding issue. Might be something with IDE or something else.
I am using Flash Develop 4.5.2 right now.
I added a small check in the class, to test equality. But it's showing strange result.
A 1 min video on Youtube about the problem => http://youtu.be/wHXs7nwyhow
![The flow jumps without getting any of the if-block][1]
[1]: http://i.stack.imgur.com/aD3YM.png
Might be some special characters issue. So, pasted it on notepad, and saved it back as ".as", but still that part is skipped by debugger. No matter, whatever i write there. ( See video )
Vishwas
Seems like a bug. I checked OFF "Omit trace actions" in Flash IDE ( So as to receive the trace statements in the trace window now ). And it's working fine now. ( It seems like Flash Develop debugger, tries ignoring those pieces of code, that are related with trace() in such case.
Related
I hope I can explain my specific annoyance clearly enough:
Quite some time ago, IntelliJ introduced a feature in the run console to parse the content of the output and would try to print a nice tree structure on the left. However, its default behavior of jumping to the error was very annoying. To illustrate my point:
When it starts normally, the full console output is available in the right panel. However, when things happen, or, in my case of gradle run, when I simply stop it, IntelliJ would jump to the specific block of output only with the error:
Note, in the second screenshot, that there is no scroll bar on the right side of the right panel, and thus I cannot scroll up to view the actual run logs. I have to click the left panel's top element in the tree to be able to view all logs.
The locking to a specific block of output is nice to have, but I am happy without it too, as before it was introduced. But the default jumping to that block is annoying and irritating. Almost in all cases I started and ended a run like this, I have to click the left panel to view the whole log -- this "Build cancelled" error block is of no use at all. And when it's jumping to an actual exception, majority of the time I'd need to look around its context for the cause, which requires me to re-orient myself in the log flow where the block was at. This is very counter productive for me.
I have been assuming IntelliJ should provide an option to either not jump to the error by default (leaving the full log available in the right panel), or to disable the whole console output parsing as a whole.
I have not been able to locate a setting for either of this. Does anyone know if that's possible?
We are working to fix that. Please vote and follow https://youtrack.jetbrains.com/issue/IDEA-241844
We have a customized mail template where we can set values of a parameter in mail preference.
After getting upgraded to Notes 9, when the parameter is set to Automatic it's working fine, but when another value is selected below thing happens (It was working fine in previous versions of Notes..):
After opening any external email, after double clicking on the mail body to edit.. notes is getting crashed.
I have two questions :
I see for external emails the control is going from querymodechange to queryclose while editing. Does it always happen?
I debugged the whole thing. Surprisingly it works in debug mode..no notes crash!!
Any help would be much appreciated !!!
This is why customizing the mail template is rarely recommended. There are interactions and dependencies between the code in the template and the Notes client, and it's very hard to debug. Since you haven't shown any of your customized code, I don't think anybody is going to be able to help you. I would recommend removing your customization code one piece at a time until it no longer crashes. Then you'll have an idea of what's triggering it, and you can try a different approach.
When Notes crashes, it dumps some diagnostics in the data/IBM_TECHNICAL_SUPPORT directory, notably the file console.log
You could review it and post here the lines pertaining to the crash.
Also, what was the previous version of Notes ?
To target the offending code line, you can use that old, dirty and tedious trick : add the folling line at the top of the QueryClose event, and move it down until you no longer see the result. Then post the context.
print now & "so far so good"
X-Post from here, for exposure: https://community.onsen.io/topic/222/monaca-ide-console-log-never-appears
Odd question, but only once while using Monaca IDE has anything ever shown up in the console.log portion of the IDE itself. It only occurred when I had a device synced via the debugger. I have since tried syncing it and I never get the device to show in the drop down box, it usually says unknown device /www/html/…
Now, do know that I have put several console.log(‘test’); lines of code to try this out and still no success. I would think that the IDE’s console area would show the log operations from the emulator and not from the device debugger as it has its own log that is view-able on the device, but this apparently isn’t the case. Is this correct or am I just really missing something simple here?
So this isn’t that big of an issue, but I figured out the problem. Basically, I keep the Monaca IDE tab open in Chrome all the time (I work via my laptop remotely). When I come back after a long absence (several hours, I don’t know what the time out is), the bottom section in the console has the Chrome error showing, like that page timed out. The IDE is still there, just that section is grayed out.
So to fix this, I would just refresh the page. The section pops back and all is good EXCEPT I just figured out that it is at that moment when the device connection no longer works. I can still click Run on Device and it works - syncing with the device - but the console.log no longer shows up. In order to get that back and working, you have to close the tab and reopen it; then everything works.
I'm not sure if this is possible. Here is an example situation:
Something is printing to my console and I don't know where it is coming from in the code. I did a quick search using the Finder in Xcode on terms such as 'NSLog' and 'print'. Nothing relevant came up.
Is there any quick way that Xcode has of finding where the source of the output is coming from ?
Kind of like when you right click on a method and you have all the options of exploring different parts of the code associated with that method.
Also: are there other functions that print besides NSLog and print?
Thanks so much!
Try running in the debugger, with breakpoints set on printf, NSLog, etc. When you hit a breakpoint do a backtrace (bt) to see where it's being called from
There's a plugin LinkedLog for that. You replace all NSLogs with LLogs and then will be able to just tap on link in Xcode's console to get to the line caused it to appear.
Didn't try it myself, but definitely will.
My application shows this error
asm CPSqliteConnectionStatementForSQL 0x30897lb3:10
and it stopped at this breakpoint in debugger
0x308971cb <+0024> mov 0x8(%edi),%eax
Does someone know about it?
The assembly code won't tell most of us anything at all, and your question is pretty light on detail about the context in which the problem occurs, such as what your app is trying to do when it crashes, whether this is always reproducible, etc. If you post more information we'll be able to help you more.
If you're debugging in Xcode, trace back up the call stack until you reach your code, then set a breakpoint there and debug your program again. When it stops at that point, try examining the related variables and see if they have the values you expect.
Edit: At the request of the asker, here is a slight clarification. When it stops at a breakpoint, the Xcode debugger window will look something like this: (from this section of Apple's Xcode Debugging Guide)
http://developer.apple.com/documentation/DeveloperTools/Conceptual/XcodeDebugging/art/debugger_disassembly.jpg
The stack frames are shown in the upper-left rectangle, and you can click on a row in the table to jump to that point in the code. Grayed-out lines are those that do not have viewable source code available. Scroll down until you see a line with black text and click on it. This will show you the point at which execution left your code and entered third-party code, and you can then examine variables to get a better idea about what the problem may be. If you have further questions, I highly recommend reading through the debugging guide linked above.