Closed
Bug 315759
Opened 20 years ago
Closed 20 years ago
Crash [@ libSystem.B.dylib.88.1.2 + 0x3008] accessing Bonjour printer settings
Categories
(Camino Graveyard :: General, defect)
Camino Graveyard
General
Tracking
(Not tracked)
VERIFIED
FIXED
Camino1.0
People
(Reporter: samuel.sidler+old, Assigned: sfraser_bugs)
References
()
Details
(Keywords: crash, fixed1.8)
Crash Data
Attachments
(2 files)
|
4.97 KB,
patch
|
sfraser_bugs
:
review-
|
Details | Diff | Splinter Review |
|
5.59 KB,
patch
|
Details | Diff | Splinter Review |
Going through the talkback reports, we have a crash when accessing a Bonjour settings page. I don't have a printer so I can't reproduce, but Mike says he has. The following are the current, relevant talkback IDs: TB11579669, TB11588817, and TB11610761. All seem to be using Camino 1.0b1 and all are on Tiger.
Also, this could become a Camino topcrash.
Comment 1•20 years ago
|
||
i can repro this 100% on all my machines with my Brother printer. New machines and upgraded machines, so it's nothing to do with the Tiger upgrade process.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•20 years ago
|
||
I don't have zeroconf printers, only CUPS sharing. The talkback stacks are pretty useless, are the stacks any better with a true debug build?
I swear we have an older bug on Bonjour/Rendezvous crashes--I remember Mike cc'ing Stuart on it--but I can't find it for the life of me (it was probably resolved WFM).
| Reporter | ||
Comment 5•20 years ago
|
||
(In reply to comment #4)
> I swear we have an older bug on Bonjour/Rendezvous crashes--I remember Mike
> cc'ing Stuart on it--but I can't find it for the life of me (it was probably
> resolved WFM).
>
Mike thought there was one as well, but I can't seem to find it.
(In reply to comment #5)
> Mike thought there was one as well, but I can't seem to find it.
Seems he filed it :-) Bug 293285.
(Apparently if you leave the --- selected in the Resolution select, it really screws up your searches)
Comment 7•20 years ago
|
||
here's the problem. we call
NSString* serviceTextRecord = [netService protocolSpecificInformation];
but:
- (NSString *)protocolSpecificInformation
This method has been deprecated. Use TXTRecordData instead.
So we're getting a nil record and don't do null checks on the data so we crash.
Comment 8•20 years ago
|
||
fix coming up.
Comment 9•20 years ago
|
||
this fixes it, but the NSData that we get back is of 0 length (which is all we need to get by the crash). I don't know if the data is of the same format as before (since my case doesn't get any) so i dunno if this is the right patch for real.
Attachment #202902 -
Flags: review?(sfraser_bugs)
Comment 10•20 years ago
|
||
Comment on attachment 202902 [details] [diff] [review]
potential patch
+#if MAC_OS_X_VERSION_MIN_REQUIRED < MAC_OS_X_VERSION_10_4
You want MAC_OS_X_VERSION_MAX_ALLOWED here. MAX_ALLOWED is the SDK version, MIN_REQUIRED is the deployment target. This is such a common mistake, I don't know why they don't just name the macros SDK and DT.
Also, does it make more sense to try TXTRecordData first and fall back to protocolSpecificInformation?
| Assignee | ||
Comment 11•20 years ago
|
||
We should revisit this Rend^H^H^H^H Bonjour code; some of it may have been obsoleted by now-available APIs.
| Assignee | ||
Comment 12•20 years ago
|
||
Comment on attachment 202902 [details] [diff] [review]
potential patch
For tiger, I think we should use [netService TXTRecordData] then [NSNetService dictionaryFromTXTRecordData:] to get the path etc. Otherwise, we fall back on our hand-parsing.
Attachment #202902 -
Flags: review?(sfraser_bugs) → review-
| Reporter | ||
Comment 13•20 years ago
|
||
Simon said he'd whip up a patch for this. This is blocking beta 2 as of now.
Flags: camino1.0? → camino1.0+
| Assignee | ||
Comment 14•20 years ago
|
||
| Assignee | ||
Updated•20 years ago
|
Assignee: mikepinkerton → sfraser_bugs
| Assignee | ||
Comment 15•20 years ago
|
||
Fixed, branch and trunk.
Updated•15 years ago
|
Crash Signature: [@ libSystem.B.dylib.88.1.2 + 0x3008]
You need to log in
before you can comment on or make changes to this bug.
Description
•