Attachments (4)
Change History (13)
by , 5 years ago
Attachment: | syslog.txt added |
---|
by , 5 years ago
Attachment: | IMG_0102.JPG added |
---|
comment:1 by , 5 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 5 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
IMO binaries built for r1b1 shouldn't be affected by the B_CLONEABLE_AREA flag policy change of a public API. It should be possible to fix in Haiku (if r1b1 binary => use always B_CLONEABLE_AREA ).
comment:3 by , 5 years ago
Writing and then applying some sort of heuristic to detect that would be pretty tricky, I don't know what you could look at to determine that. But even if there was, is it worth the time and effort to fix one application? If there were a lot more that might make sense, but so far no others have been reported.
comment:5 by , 5 years ago
That would require fetching the image of the return address before every create_area, which would complicate the code significantly; or in the case where we used __gABIVersion
, it would pick the oldest version, which would always be a pre-beta2 image, making the clone_area changes useless.
I still maintain that if cdrecord is the only affected application, we should just add some patch to it (or even just wait for the beta2 branch cut) and move on.
comment:6 by , 5 years ago
I tried to get a little more info.When attempting to burn a cd, cdrecord crashes. After that, it is impossible to eject the disc unless cdrecord -eject is invoked from the CLI. I attached debugger to cdrecord in this case. Debug reports attached.
by , 5 years ago
Attachment: | cdrecord-17714-debug-02-09-2019-00-54-50.report added |
---|
by , 5 years ago
Attachment: | cdrecord-17715-debug-02-09-2019-00-53-00.report added |
---|
comment:8 by , 5 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Change merged in hrev53495.
comment:9 by , 5 years ago
Milestone: | Unscheduled → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
It appears cdrecord is actually using BeOS areas internally for operation. They now need to have the B_CLONEABLE_AREA flag applied; please open a bug at HaikuPorts.