[haiku-development] Re: BeOS Apps Crashing on Haiku (Bug #889)
- From: Oliver Tappe <zooey@xxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 31 May 2007 22:09:12 +0200
Hi there,
On 2007-05-31 at 17:31:58 [+0200], Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
wrote:
>
> On 2007-05-31 at 16:55:35 [+0200], Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
> wrote:
> > Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> > > Besides ignoring the problem I see the following possible solutions:
> > >
[ ... ]
> > Nice problem we ran into there :-)
Oh yes, indeed ;o)
Ingo, I am pretty sure that the problem you have described is precisely the
reason why I had to introduce some "specialty" to gcc-2.95.3-beos that would
fix crashing problems related to type_info of BDirectWindow (by providing a
separate correct type_info function in a special object file).
Very good work! :o)
> > I would actually think it would be best to implement both options; 1)
> > because it'll definitely solve the problem and makes us compatible with
> > BeOS - we could make the change a compiler option
>
> Come to think of it, if the loader was able to find out what compiler has
> generated the shared objects involved, it could even decide live what
> strategy to use.
I suppose the loader could look into the .comment section and find out this
way:
objdump -s -j .comment /bin/ls
yields (lots of) string containing '.GCC: (GNU) 2.9-beos-991026', unless I'm
mistaken, the section contains one such string for each object file contained
inside of the shared object.
cheers,
Oliver
Other related posts:
