Hello, Sebastian Humenda, le mar. 05 nov. 2024 10:52:19 +0100, a ecrit: > With BRLTTY 6.7, BRLTTY crashed while I was using Orca in the X session. The > back trace is below.
> Thread 1 (Thread 0x7f2092ffe6c0 (LWP 589460)): > #5 0x00007f20963ec7ba in malloc_printerr (str=str@entry=0x7f20964ef0b1 > "free(): invalid pointer") at ./malloc/malloc.c:5660 > #6 0x00007f20963ee544 in _int_free (av=<optimized out>, p=<optimized out>, > have_lock=have_lock@entry=0) at ./malloc/malloc.c:4435 > #7 0x00007f20963f0e9f in __GI___libc_free (mem=<optimized out>) at > ./malloc/malloc.c:3385 > #8 0x00005637596a87bc in freeKeyrangeList (l=l@entry=0x7f2084025ce0) at > ../../Programs/brlapi_keyranges.c:65 > #9 0x00005637596a12c6 in doLeaveTty (c=c@entry=0x7f2084025c50) at > ../../Programs/brlapi_server.c:993 So it'd either be a concurrent operation on c->acceptedKeys, or a memory corruption from somewhere else. This code has not really changed since 6.6, so it seems unlikely to me (and I have re-proofread it), so I'd tend to think about "somewhere else". Ideally you could run it through valgrind, but that'd probably be way too heavy. Perhaps you can recompile with CFLAGS=-fsanitize=address LDFLAGS=-fsanitize=address ? Samuel _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://brltty.app/mailman/listinfo/brltty
