Building on android - compiled program segfaults
nathan.huesken at posteo.de
Fri Jan 11 16:13:44 CET 2013
Ok, there I was a stupid.
When I flush stdout I see the output of those printfs.
The segfaults happens somehwere else (see the other answers).
On 01/11/2013 02:31 PM, Ian Lynagh wrote:
> On Fri, Jan 11, 2013 at 12:36:22PM +0100, Nathan Hüsken wrote:
>> And now I am clueless. So I tried the good old printf debugging in the
>> rts. Using this, I see that it gets before the call to
>> scheduleWaitThread in the function rts_evalLazyIO (in RtsAPI.c).
>> But when I put a printf in the beginning of scheduleWaitThread (in
>> Schedule.c) it is not shown.
>> What else can I do to find out more?
> Sounds like it would be useful to set a breakpoint on rts_evalLazyIO,
> disassemble, then "si" through the call to scheduleWaitThread to see
> what's happening. "info register someregistername" will tell you what's
> in someregistername.
More information about the ghc-devs