-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix NPE segfault when "verbose" is enabled #96
Conversation
Prior to revision b606826, log_tag() was only ever invoked when err_fp was guaranteed to be assigned. After that revision, it could be called with err_fp being null. Carry some of the old "!verbose" logic into log_tag() to address this.
This may be unrelated to #94. I haven't tested that one. The stack Running "pkgin -V upgrade mate" (on a local repo, not that that $ pkgin -V upgrade mate 156 packages to refresh: 78 packages to upgrade: 1 package to install: 156 to refresh, 78 to upgrade, 1 to install proceed ? [Y/n] y $ gdb /usr/pkg/bin/pkgin ./pkgin.core |
Thanks! Will look at this today. FWIW there's no such thing as |
It's also worth mentioning that, as described in #102, the |
Yeah, once I actually used it, and looked at what it was doing, I was puzzled, because it wasn't what I thought I'd get. That was my first time really using pkgin for anything, so I wanted as much detail as possible about what it was doing. Anyway, good you've opened #102, thanks! |
Prior to revision b606826, log_tag() was only ever invoked when err_fp
was guaranteed to be assigned. After that revision, it could be called
with err_fp being null. Carry some of the old "!verbose" logic into
log_tag() to address this.