Building documentation failing. "/bin/sh failed with exit code 250" #430

Closed
Ziewvater opened this Issue Feb 23, 2014 · 4 comments

Projects

None yet

4 participants

@Ziewvater

Getting a build failure trying to run appledoc through Xcode on my project. Previous to this issue, building my documentation did not have any issues, and have been built successfully.

It's been a while since I've built my documentation so I don't really know what kind of change I might have made that has caused appledoc to run into this issue. The failure message is as follows:

2014-02-23 13:59:24.183 appledoc[2598:507] -[GBEnumConstantData methodSelector]: unrecognized selector sent to instance 0x40104d440
appledoc version: 2.2 (build 961)

Oops, something went wrong...
NSInvalidArgumentException: -[GBEnumConstantData methodSelector]: unrecognized selector sent to instance 0x40104d440
  @ 0   CoreFoundation                      0x00007fff8b6e241c __exceptionPreprocess + 172
  @ 1   libobjc.A.dylib                     0x00007fff888ffe75 objc_exception_throw + 43
  @ 2   CoreFoundation                      0x00007fff8b6e52ed -[NSObject(NSObject) doesNotRecognizeSelector:] + 205
  @ 3   CoreFoundation                      0x00007fff8b6405b2 ___forwarding___ + 1010
  @ 4   CoreFoundation                      0x00007fff8b640138 _CF_forwarding_prep_0 + 120
  @ 5   appledoc                            0x000000010a714b49 appledoc + 154441
  @ 6   appledoc                            0x000000010a718b5a appledoc + 170842
  @ 7   appledoc                            0x000000010a718813 appledoc + 170003
  @ 8   appledoc                            0x000000010a717504 appledoc + 165124
  @ 9   appledoc                            0x000000010a715915 appledoc + 157973
  @ 10  appledoc                            0x000000010a7152f7 appledoc + 156407
  @ 11  appledoc                            0x000000010a714f4f appledoc + 155471
  @ 12  appledoc                            0x000000010a71be8f appledoc + 183951
  @ 13  appledoc                            0x000000010a71b662 appledoc + 181858
  @ 14  appledoc                            0x000000010a71adec appledoc + 179692
  @ 15  appledoc                            0x000000010a6f297c appledoc + 14716
  @ 16  appledoc                            0x000000010a6f12f3 appledoc + 8947
  @ 17  appledoc                            0x000000010a6f14d7 appledoc + 9431
  @ 18  appledoc                            0x000000010a6f09d4 appledoc + 6612
Showing first 200 notices only
Command /bin/sh failed with exit code 250

It seems like there might be something going wrong when trying to parse documentation around an enum constant, but I don't really know what to look for. Does anyone have experience with errors like this that can shed some light on it?

@tomaz
Owner
tomaz commented Feb 24, 2014

It probably gets tripped over some source - increase verbosity with --verbose 6 to identify the source of the problem.

@robvdveer
Collaborator

Let me know in which file it trips and please attach the sourcecode. Perhaps it is just a syntax issue.—
Sent from Mailbox for iPad

On Mon, Feb 24, 2014 at 7:25 AM, tomaz notifications@github.com wrote:

It probably gets tripped over some source - increase verbosity with --verbose 6 to identify the source of the problem.

Reply to this email directly or view it on GitHub:
#430 (comment)

@Ziewvater

So I was able to fix my issue and I think I might have found what was causing the problem. First, however, I just want to say that setting verbose 6 put out way too much stuff and the log file seemed to get cut off without giving me a clue where the problem was happening. Using verbose 5 instead provided enough information that I was able to pinpoint my issue.

The problem seems to have been that I was referencing a different enum type within the documentation on a enum type value. That is, within the documentation for a specific enum value (e.g. AnEnumTypeValue of type AnEnumType, defined using NS_ENUM(NSInteger, AnEnumType)), another enum type was mentioned (e.g. AnotherEnumType). Removing this mention stopped appledoc from failing.

It should be noted that it was only when mentioning the overall type in the documentation that appledoc failed to build. If I were to mention a specific enum type value (e.g. AnotherEnumTypeValue of type AnotherEnumType), the build would complete without errors.

@tomaz tomaz closed this May 16, 2014
@caseycoding

Thanks for updating this with your resolution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment