***karlosz_ is now known as karlosz
***apteryx is now known as Guest80643
***apteryx_ is now known as apteryx
<leoprikler>It appears `false-if-exception' does not catch exceptions when used inside `with-exception-handler' (but it does inside `with-throw-handler'). <leoprikler>(with-exception-handler (lambda _ (display (false-if-exception (error "moo")))) (lambda () (error "meow"))) <leoprikler>(with-throw-handler #t (lambda () (error "meow")) (lambda _ (display (false-if-exception (error "moo"))))) <leoprikler>The first will backtrace on "moo", the second on "meow" <lampilelo>what's up with this "#define FUNC_NAME s_function_name" it's not documented in the info manual but is required for some macros that are documented there (like SCM_ASSERT_TYPE) <dsmith>It's so some error messages can show the current C function <lampilelo>ah, no' its not for SCM_ASSERT_TYPE, it's required for internal macros <lampilelo>so what would I give SCM_ASSERT_TYPE as a subr argument in normal code not internal to guile? just "function-name"? <dsmith>#define SCM_ASSERT_TYPE(_cond, _arg, _pos, _subr, _msg) <dsmith>Since a SCM can be any type, those ASSERT's are usually used on entry to a C function to ensure that the args are what the function can handle. <dsmith>Usually called right at the entry to the function. <dsmith>the _pos is the argument number. <lampilelo>what i'm really asking is what is this s_function_name thing? i see now that snarfing my SCM_DEFINE created an entry that uses it <dsmith>Oh. That's a static string with the function name. <lampilelo>i'm interested because in reality I tried to use SCM_VALIDATE_HOOK macro and it requires FUNC_NAME <lampilelo>but it's not documented so i'm assuming it's considered an internal macro and isn't designed to be used outside guile <lampilelo>ah, ok, i found where it's defined, so it just assigns scheme function name to it <leoprikler>I think the convention is to use {\n#define FUNC_NAME ...\n...\n#undef FUNC_NAME\n} <dsmith>Well, if you look at just about any source file in libguile, you can see that FUNC_NAME is #define'ed and #undef'ined for every C func. <lampilelo>leoprikler: sure, it's a convention in a guile source tree but it's not documented so, like i said, i'm assuming it isn't meant to be used outside <leoprikler>perhaps not the nicest interface for extensions, but probably not one that's going to collide with other stuff <leoprikler>well, neither is the SCM_VALIDATE_HOOK macro, so... <lampilelo>and that's why i started looking for an alternate way, but SCM_ASSERT_TYPE requires a _subr <lampilelo>so i wanted to know how it all falls together <dsmith>While useful for external C modules, I don't think those assert macros (and snarfing macros) where written with *external* modules in mind. More to just make libguile code eaiser to manage. <leoprikler>Snarfing is partially documented for external modules. <rekado>I’m running a debug build of Guile Emacs in gdb to analyze some segfaults and other bugs, but I don’t understand exactly what I’m looking at. <dsmith-work>rekado: I'm guessing #15 is where the problem starts: <dsmith-work>handler=<error reading variable: ERROR: Cannot access memory at address 0x2>0x7ffff31614c0 <rekado>Cannot access memory at address 0xfffffffffffffe00 <rekado>this looks like it happens really early, right after using scm_with_guile <dsmith-work>So #21 is in the GC. Maybe that's looking somewhere it shouldn't? <rekado>hmm, I’ll rebuild with libgc 7 instead of 8. <lampilelo>it seems like it segfaults while catching an error inside a finalizer <dsmith-work>Unfortuantely, that happens a lot. A segfault within an error handler. <dsmith-work>main code: Ooo look! I got an error trying to read this address! <dsmith-work>error handler: Ok, let's print out what's at that address.. <mwette>Hey guys, 0xfffffffffffffe00 looks like it could be -1 immediate value. How many bits does Guile use for marking values? <mwette>Look at the section "Faster Integers" in the Guile Ref Manual. <mwette>Ah, 3 bits. That's not -1 methinks. <lloda>I think I'm going to remove the bug list & new bug tabs in the guile-cairo website and just direct people to guile-user. This thing is pretty stable and we don't get many bugs. All the bugs in the old tracker are fixed. Wdyt wingo? <catonano>can I build just the Guile manual and not Guile itself ? <wingo>catonano: after configuring i would guess "make -C doc" <lampilelo>hmm, is string-titlecase supposed to turn "i'm" into "I'M"? <lampilelo>string-locale-titlecase handles it correctly and turns it to "I'm" <lampilelo>it doesn't seem to matter but i have LANG set to en_US.UTF-8, but the LC_* pl_PL <lampilelo>but when i overwrite it and run it again it doesn't change <lampilelo>on srfi.schemers.org they specify "if c is preceded by a cased character, it is downcased; otherwise it is titlecased", so i guess it's right *dsmith-work acivates his portable snarkulator <rekado>guile-emacs fails with the same kind of error when linked with libgc-7.6.12 ***jao is now known as Guest77108
<sneek>I think I remember bipt in (here?) 9 months ago, saying: i saw that your guile-emacs package made it into a guix release :). <civodul>ZombieChicken: janneke is one of the people who looked into it <civodul>ArneBab_: you've been having networking issues :-) <janneke>hey ZombieChicken, there is a wip-pinebook-pro branch <janneke>currently, vagrantc (over at #guix) is oloking into it (my pbp is dead) <janneke>hehe, dunno why that happens some times <cbaines>janneke, what happened to your Pinebook Pro? <cbaines>(I ordered one, and I'm hoping it'll be shipped soon) <janneke>cbaines: i have no idea, i liked it a lot