BUG: Fix segfault in lib.isnullobj
Weird segfault arises when you call `lib.isnullobj` with an array that uses 0-field values to mean `None`.
Changed input to be a `Python` object (i.e. no typing), and the segfault went away.  Discovered when there were segfaults in printing a `DataFrame` containing such an array.

Closes #13717.

## [Current coverage](https://codecov.io/gh/pydata/pandas/pull/13764?src=pr) is 84.56% (diff: 100%)

> No coverage report found for **master** at b60e42b.
> 
> Powered by [Codecov](https://codecov.io?src=pr). Last update [b60e42b...cd07769](https://codecov.io/gh/pydata/pandas/compare/b60e42b02040624f319cadd60a99fe50eb62d62e...cd077693d209e575fc6a8e806b7470e47cac4349?src=pr)
 you need to check if it's iterable now eg s scalar will fail 
 or at least assert that (as this cannot be called with s scalar)
 @jreback : good point about the scalar thing - I think I actually don't need to remove `ndarray` entirely.  If I remove the `object` dtype specification, that might be sufficient.  Testing it right now.
 @jreback : "fixed" all four `isnullobj` methods and added tests for all of them, and Travis is still passing.  Ready to merge if there are no other concerns.
 lgtm. can you give a perf test and see if anything material (I don't think so, but can't hurt). as this is the null tester for strings.
 What do you mean `null` tester for strings?  What method are you referring to?
 this is called for null testing on strings
 From where exactly?  Are you talking about the `pandas.types.missing` methods (also, why focus on strings specifically?)
 look at how isnull works. this is the only 1 of 2 places this is called.
 Okay, that's what I thought.  Where should this perf test go in `asv_bench`?  In `strings.py` I presume?
 oh, i mean there prob is a benchmark that tells null on strings already, if not see where the null tests are (I _think_ they are all in one place).
 @jreback : I found `isnull` benchmarks in the `DataFrame` benchmarks, so I added one for strings there.
 Travis is doing weird things.  Putting `[ci skip]` in the commit until it corrects itself.
 thanks

minor change I made in the asv
also it IS slightly slower, so I guess the emitted c-code is slightly less optimal w/o the object typing (but can't have seg faults of course :)
