[haiku-development] Re: weird segfault in malloc internals when trying to call fdopen()
- From: Michael Zucchi <notzed@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 18 Oct 2009 16:35:46 +1030
Hi there,
FWIW I got emacs to compile and run (in terminal mode). I disabled
dumping because I didn't know enough about haiku to make it work.
If you're interested I can send you my s/haiku.h - basically I kept
turning stuff off/mucking about till I got it to work, but it was
mostly random with no prior knowledge so it is unlikely to be
particularly well done.
Michael
2009/10/17 François Revol <revol@xxxxxxx>:
>> #define SYSTEM_MALLOC
>>
>> \o/ \o/ \o/
>
> Great.
>
> I probably had to force something alike in XEmacs as well though I
> don't recall it.
>
>> Which makes emacs use system malloc instead of its own malloc
>> infrastructure.
>> Supposidly the emacs malloc is ``better,'' for some value of that,
>> but not
>> segfaulting is better to me.
>
> It probably makes bad assumptions about [s]brk() and other stuff...
>
>> trying to unexec the bootstrapped temacs also fails with:
>>
>> emacs: .bss shrank when undumping???
>
> Maybe some missing sections.
>
> Doesn't Emacs have a portable dumper like XEmacs ?
>
> IIRC you must force it somewhere.
>
> Checked my patches ?
> Oops, the old ones are not around.
> I'll track the last one I made and upload it.
>
>>
>> which is probably just some nuance of Haiku's ELF implementation I
>> need to try and account for. I'll get to that once I figure out
>> what's
>> up with the terminal.
>
> I really didn't even try to do it, I didn't want to learn about ELF at
> the time ;)
>
> François.
>
>
Other related posts:
