#14129 closed bug (fixed)
TLS/pthread crash
Reported by: | miqlas | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | System/libroot.so | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86-64 |
Description
Since some days i experience strange crashes with "ag" (the silver searcher) on the new laptop.
It worked very well with the old one and except the hardware nothing changed (but maybe i updated some Haiku revision without noticing this)
It is possible that it is a bug in Ag, which got not triggered on the earlier slow hardware but happens on the new wich much faster.
Tried to build it with -g and using with LD_PRELOAD=libroot_debug.so, even with Ag's own -D debug flag.
See the attached crashlogs.
Attachments (4)
Change History (15)
by , 7 years ago
Attachment: | ag-12176-debug-08-05-2018-06-33-37.report added |
---|
by , 7 years ago
Attachment: | ag-12218-debug-08-05-2018-06-34-24.report added |
---|
Crashlog - _kern_mutex_lock
by , 7 years ago
Attachment: | ag-11952-debug-08-05-2018-06-28-53.report added |
---|
Crashlog - get_tls_address
by , 7 years ago
Attachment: | ag-12096-debug-08-05-2018-06-32-38.report added |
---|
Crashlog - FreeChunk::Size
comment:1 by , 7 years ago
Btw: Ag is in Haikuports, that is the one wich is crashing. Tested with earlier version, they are crashing too. Never ever happend this before, i'm sure, as it is one of my main productivity-tool i use it really extensively and used every earlier version from the HaikuPorts repo on x86_64 so no arch change happend.
comment:3 by , 7 years ago
I created an issue at "Ag" github too: https://github.com/ggreer/the_silver_searcher/issues/1235
comment:4 by , 7 years ago
Replying to korli:
which hpkgs are installed?
https://depot.haiku-os.org/#!/pkg/the_silver_searcher/haikuports/2/1/0/-/1/x86_64?bcguid=bc260-PKMU
comment:5 by , 7 years ago
I'm not well educated in reading backtraces, so maybe it is normal, but my gut says something wrong happens here as i see backtrace output mixed with freebsd sources. (I searched for something in the freebsd source tree as it happend)
follow-up: 7 comment:6 by , 7 years ago
I mean the list of hpkgs.
comment:7 by , 7 years ago
Replying to korli:
I mean the list of hpkgs, or a syslog.
Can't provide it right now. Will do later.
Is it possible to tell from this backtraces if it is a bug in Ag or in Haiku?
comment:8 by , 7 years ago
Not exactly, you could try an older version of Haiku to check if a Haiku update triggered these crash.
comment:9 by , 7 years ago
Tested with earlier Haiku nightly: crashes. Maybe the newer hardware triggers something somewhere.
comment:10 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed in hrev52662 (and fix merged into r1beta1 also.)
comment:11 by , 5 years ago
Milestone: | Unscheduled → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
Crashlog - DynamicThreadVector