> On Thu, Oct 23, 2014 at 14:11:43 +0200, Christian Lepper wrote: > > > Interesting, this has never managed to hit us before and we cross- > > > compile lots > > > of stuff. Well spotted. > > Should i do a bug to mantis? Just registered @ > > http://bugs.netsurf-browser.org/mantis/my_view_page.php > > Please :-)
Done ;-) > > > I'm afraid I'm not au-fait with fbtk, but perhaps Michael Drake can > > > jump in here. > > > I suggest you report this compile error on the mantis too. And Done ;-) > > > Font rendering for the framebuffer frontend is handled by NS > separately > > > from the framebuffer physical layer. > > > Adding SDL-ttf would imply making NetSurf's codebase have SDL > content. > > > Perhaps better would be to push more of the > > > font rendering into libnsfb and then the option would open up. > > > > Ah okay, understood. If this point is getting interesting let me know > about. > > Were using SDL intensively and a lot of its children like: > > (SDL-ttf, SDL-gfx, SDL-image, SDL-mixer, SDL-net) > > Maybe i can help at this point. > > If you want to help improve libnsfb we'd be very pleased to see patches > :-) Will try to do so. > > > Yes, spent several hours getting libmozjs-24.2 make'd. > > But i think its mostly a problem of its configure/makefiles. > > Later today will use 18.x and check this. > > We have the need to get js working, > > cause we want to add our hardware stuff > > in there to get the hardware-data > > (like AD/Timers/Counters/gpio...) > > to the Screen/Browser. > > Our JS support is *very* rudimentary for now, > and I wouldn't expect you to want > to rely on it working. Again, if you wanted to help with this part of > NetSurf we'd love patches. > Currently most (or all) of the JS work is done by > Vincent Sanders who is overworked and underappreciated by us all :-( Oh i see. Will try to help ;-) > > > Maybe the line @(0.894468)... is interesting? There is no user.css > inside > > the resources. > > user css is usually not an issue. > > > (0.807875) content/content.c content_add_user 601: content > > http://www.google.de/ (0x2af078), user 0x1419c 0x28d7b0 > > desktop/browser.c:browser_window_callback:1377: chris > > browser_window_callback_errorcode:1123: chris > > messages_get_errorcode:282: NSERROR_BAD_ENCODING > > (0.825468) framebuffer/misc.c warn_user 30: BadEncoding (null) > > This is certainly the error location. I'd be tempted to get gdb > involved, > breakpoint on the error handler in the browser_window_callback routine, > and > then examine the stack to see if I could work out where the error was > coming from. I already tried to include glibs backtrace / backtrace_symbols mechanism which i use in my applications. But it didnt work (dont know why in the moment). I havent used yet gdb on the target and am not really familiar with it ;-( I figure out more Infos.... Yours Chris
