Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#5135 closed bug (fixed)

BeIDE not started

Reported by: Michael S. Owned by: axeld
Priority: normal Milestone: Unscheduled
Component: Kits/Media Kit Version: R1/Development
Keywords: BeIDE Cc:
Blocked By: Blocking:
Platform: x86

Description

BeIDE from BeOS R5 Development Tools not started on Haiku R34640 and newer, though worked earlier normal.

Welcome to the Haiku shell.

/boot/apps/BeIDE> BeIDE
runtime_loader: /boot/apps/BeIDE/BeIDE: Could not resolve symbol 'Subscribe__11BSubscriberP21BAbstractBufferStream'
resolve symbol "Subscribe__11BSubscriberP21BAbstractBufferStream" returned: -2147478780
runtime_loader: /boot/apps/BeIDE/BeIDE: Troubles relocating: Symbol not found
/boot/apps/BeIDE> 

Change History (7)

comment:1 by bipolar, 14 years ago

It seems to be related to the changes on hrev34505.

comment:2 by bonefish, 14 years ago

Component: ApplicationsKits/Media Kit
Owner: changed from nobody to axeld

Absolutely. Reassigning to the one to blame.

comment:3 by axeld, 14 years ago

Status: newassigned

comment:4 by axeld, 14 years ago

Resolution: fixed
Status: assignedclosed

Fixed in hrev34688.

comment:5 by Michael S., 14 years ago

Resolution: fixed
Status: closedreopened

Again not started on hrev35340 2/4:

Welcome to the Haiku shell.

/boot/apps/BeIDE> BeIDE
runtime_loader: /boot/apps/BeIDE/BeIDE: Could not resolve symbol 'FSGetDeskDir__8BPrivateP10BDirectoryl'
resolve symbol "FSGetDeskDir__8BPrivateP10BDirectoryl" returned: -2147478780
runtime_loader: /boot/apps/BeIDE/BeIDE: Troubles relocating: Symbol not found
/boot/apps/BeIDE> 

comment:6 by anevilyak, 14 years ago

Resolution: fixed
Status: reopenedclosed

Please file a new ticket instead of reopening this one, as this is a different problem: this is a (private) libtracker symbol that was recently reworked, which BeIDE shouldn't have been using in the first place...will have to think about that though.

comment:7 by anevilyak, 14 years ago

Should work again as of hrev35428.

Note: See TracTickets for help on using tickets.