Closed
Bug 291420
Opened 20 years ago
Closed 20 years ago
build.dat can't be read because |tell| returns 0
Categories
(Webtools Graveyard :: Tinderbox, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ajschult784, Assigned: ajschult784)
References
()
Details
Attachments
(1 file)
|
809 bytes,
patch
|
chase
:
review+
|
Details | Diff | Splinter Review |
I discovered that my builds weren't showing up because |tell| here: http://lxr.mozilla.org/mozilla/source/webtools/tinderbox/Backwards.pm#47 returns 0, even though my build.dat contains data. info at the URL above includes: > Do not use tell() (or other buffered I/O operations) on a file handle that has > been manipulated by sysread(), syswrite() or sysseek(). Those functions ignore > the buffering, while tell() does not. sysseek returns the position. Is there any reason not to use it?
| Assignee | ||
Comment 1•20 years ago
|
||
Attachment #181506 -
Flags: review?(chase)
Updated•20 years ago
|
Attachment #181506 -
Flags: review?(chase) → review+
| Assignee | ||
Comment 2•20 years ago
|
||
fixed
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•