I am told that this NPDA is wrong but I can't see why, could anyone spot the bug?
Related
I'm not sure where this should be posted but I have a suggestion for Google Docs. My elementary school children are learning to write and I believe it would be beneficial if Docs would point out when their spelling or grammar is wrong via underlining, as is the case now. However, it would be nice if the suggestions could be turned off so that the student is informed something is wrong but they need to be the one to retry until they get it right. Simply clicking the suggestion does not lead to greater understanding. Would this be possible? Thank you,
Chris Barnes
e
I have looked through DarkRP code to learn to create my own addons and game modes. I am trying to understand all that is happening and I have seen fn.id many times and fail to understand what it means. Anyone who can point me in the right direction I would appreciate it :)
fn.Id is the identity function, from the fn module. It returns the arguments passed to it.
I am trying to instrument C code with ANTLR listener mechanism. But I found some inconsistent behavior of the TokenStreamRewriter.InsertBefore() API with the C do-while(); statement.
I have posted a detailed description as ANTLR Issue #2252. So I won't duplicate it here.
Anyone met the same issue?
Issue solved. Turns out my assumption of the behavior of InsertBefore/After() is incorrect. I posted the detailed explanation to the Issue #2252. Hope it can help someone as confused.
I got an EXC_BAD_ACCESS in my iOS program, and I suspect that the cause is in one of my anonymous blocks, but there are quite a few of those, and I need to narrow down the candidate list a bit.
The stack trace shows the current frame as __lldb_unnamed_function4866$$ProjectName. There are no line numbers or source file names that I can see. No local variables visible either. The debugger shows machine code instructions. This was running on a background event queue, so there is none of my code anywhere else on the stack.
How do I go about finding out what function this is?
I came across a similar situation, and while I can't help (yet) with your problem, I think I know a man who can.
Check out http://www.realmacsoftware.com/blog/block-debugging, for an exposition of how to find out a lot more about the evil block in question.
It doesn't help me much, because I'm working from a crash log, but if you're still interested, this is going to give you just about as much as you can get about the unnamed block.
Warning, the above link exposes you to a lot of arcane knowledge, and may make you feel a little inadequate :)
[Editted to add]
Not good enough yet?
After searching through disassembly and doing some manual symbolication, I came to the conclusion that the ___lldb_unnamed_function is a red herring.
I followed How to manually symbolicate a crash log with atos, and it pointed the finger at a completely different function, which came from a 3rd party library, and was a very good candidate for the crash reason (killed by angry watchdog with badf00d.)
In the course of this enquiry, I also came across hopper, a great disassembler; I used the demo version to confirm what the suspicious code was doing, so I'm giving them a namecheck.
Try to set an exception breakpoint by clicking on the plus symbol within the breakpoint navigator cmd + 6.
For getting an overview of debugging best practices if found it useful to consider a Stanford Lecture on iTunes U
So, this is probably a really, really stupid question. :/ Sorry about that, I'm a total newbie. Um, I'm getting a lot of "invalid byte sequence in UTF-8" type errors. I found a solution here (scroll down for the +24 one), but I have no idea how to actually implement it. Do I type it in the head of the affected files? Do I have to install anything else? Also, which solution is better, the ignore one or the double-encoding one?
Also bonus noob question! The code I'm fiddling with now is actually shared code, which means that it's presumably worked for a lot of other people without the UTF-8 problem. Any idea why my computer especially seems to be unable to get it working? Thanks.
Just put
# encoding: utf-8
on the very first line of affected files.