Opened 10 years ago
Last modified 10 years ago
#11635 new bug
A pair of BeOS apps doesn't work on Haiku
Reported by: | Giova84 | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Applications | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
Hi, there are two media applications (Dynamic Composer and Rack747) which doesn't work on Haiku: when I attempt to run them on Haiku, these apps just crash. Unfortunately these apps are closed source, so I don't know if there is some hope to see them properly run on Haiku.
These apps are available here: http://softwaredepot.xoom.it/upload/beos_apps/dynamiccomposer.zip http://softwaredepot.xoom.it/upload/beos_apps/rack747-1.45-x86.pkg
Debug reports attached.
Attachments (2)
Change History (6)
by , 10 years ago
Attachment: | DynamicComposer-1203-debug-18-12-2014-19-51-33.report added |
---|
by , 10 years ago
Attachment: | Rack747-1312-debug-18-12-2014-19-54-00.report added |
---|
follow-up: 2 comment:1 by , 10 years ago
comment:2 by , 10 years ago
Replying to pulkomandy:
The first one crashes in BString, it looks like the BString object was not properly constructed (the fPrivateData is NULL and this shouldn't happen) or the object was overwritten (use-after-free or reference to out of scope stack object).
So, assuming this issue, there could be a fix to be implemented in Haiku, to properly launch Dynamic Composer?
comment:3 by , 10 years ago
I don't know what the problem exactly is. I looked at BString code and couldn't find a way it could intentionally get in that state, so I'm assuming the memory was overwritten by something else. We could avoid the crash but I doubt it would go much further if something went wrong.
comment:4 by , 10 years ago
It's not unlikely that it's an internal app bug that just happened to not get triggered in BeOS due to differences in address mapping or private implementation, it wouldn't be the first time.
The first one crashes in BString, it looks like the BString object was not properly constructed (the fPrivateData is NULL and this shouldn't happen) or the object was overwritten (use-after-free or reference to out of scope stack object).
The second one crashes in what appears to be application code, hard to tell more then.