https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276319
Bug 276319 depends on bug 277928, which changed state.
Bug 277928 Summary: www/py-django-ldapdb: Deprecate/Set to expire
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277928
What|Removed |Added
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278560
Bug ID: 278560
Summary: www/chromium 124.0.6367.60 on 13.2-RELEASE-p10 compile
failure
Product: Ports & Packages
Version: Latest
Hardware: Any
OS:
Bugzilla Automation has asked freebsd-chromium (Nobody)
for maintainer-feedback:
Bug 278560: www/chromium 124.0.6367.60 on 13.2-RELEASE-p10 compile failure
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278560
--- Description ---
./../third_party/ffmpeg/libavutil/thread.h:228:19: error:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278430
Cy Schubert changed:
What|Removed |Added
Attachment #250047|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278430
--- Comment #1 from Ed Maste ---
This was fixed along with other changes in upstream
https://github.com/heimdal/heimdal/commit/c1c7da7f79d79861a9c48af0a4d5a6734ea0da70
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278480
--- Comment #3 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=14e3f2d8d3eb6f47556e59bee3e2004ac9a9d7e6
commit 14e3f2d8d3eb6f47556e59bee3e2004ac9a9d7e6
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278480
--- Comment #2 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=4f223e0da7b4a055d9416f9161b44ffed765a9c3
commit 4f223e0da7b4a055d9416f9161b44ffed765a9c3
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262856
--- Comment #7 from Friedrich Volkmann ---
My mainboard is an MSI Z97S SLI Plus with Intel Z97 Express (Haswell) chipset.
My guess is that the onboard GPU makes the memory architecture non-uniform by
occupying some of the system RAM.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257173
Jung-uk Kim changed:
What|Removed |Added
Assignee|b...@freebsd.org|ke...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257310
Mark Linimon changed:
What|Removed |Added
Keywords|needs-qa|honeypot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278529
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262856
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #6 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278348
Gleb Smirnoff changed:
What|Removed |Added
CC||gleb...@freebsd.org
--- Comment
Bugzilla Automation has asked freebsd-ruby (Nobody)
for maintainer-feedback:
Bug 278554: lang/ruby33: /usr/bin/install: ChangeLog: Inappropriate file type
or format
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278554
--- Description ---
Staging lang/ruby33 after this commit[0] to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278554
Bug ID: 278554
Summary: lang/ruby33: /usr/bin/install: ChangeLog:
Inappropriate file type or format
Product: Ports & Packages
Version: Latest
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278553
Antoine Brodin changed:
What|Removed |Added
Assignee|ruby@FreeBSD.org|port...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278553
Bug ID: 278553
Summary: [exp-run] lang/ruby32: Update to 3.2.4
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Bugzilla Automation has asked freebsd-ruby (Nobody)
for maintainer-feedback:
Bug 278553: [exp-run] lang/ruby32: Update to 3.2.4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278553
--- Description ---
Ruby 3.2.4 is release as latest versin of Ruby 3.2 series. Since lang/ruby32 is
current
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255337
--- Comment #37 from Adrian Chadd ---
It's a USB device, not a PCI device!
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262856
--- Comment #5 from Friedrich Volkmann ---
I managed to resolve this for me by adding the options from the MINIMAL kernel
that weren't in my custum kernel. I think the culprit was I had to add:
optionsNUMA
I don't know what
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278524
--- Comment #4 from Dmitry Lukhtionov ---
I rebooting notebook and see
root@acer:/home/mitya # ifconfig wlan0 scan
SSID/MESH ID BSSID CHAN RATES:N INT
CAPS
Altair free_5G
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262856
--- Comment #4 from Ed Maste ---
There is insufficient information to make progress here. At a minimum you'd
need to build a kernel with KDB and KDB_TRACE options to print a backtrace upon
panic. If you're no longer in a position to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278524
--- Comment #3 from Dmitry Lukhtionov ---
I see 'Enabling WB225 BTCOEX' in dmesg
but `ifconfig wlan0 scan` and `ifconfig wlan0 list scan` produce empty output
Can I debug this error ?
`ar9300_hw_attach: ar9300_eeprom_attach returned 0`
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262856
Ed Maste changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278399
Ed Maste changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278399
--- Comment #3 from Friedrich Volkmann ---
i remember clearly that I added the attachment, and even Firefox remembers the
description i typed in. The reason why the upload failed is certainly the size
limit. Now that I uploaded the file
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278399
--- Comment #2 from Friedrich Volkmann ---
Created attachment 250176
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=250176=edit
output of make buildkernel KERNCONF=GENERIC
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278546
--- Comment #1 from Ivan Rozhuk ---
This code may be guarded by condition:
#if (sizeof(int) + sizeof(void*)) != sizeof(struct fiodgname_arg)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278546
Ivan Rozhuk changed:
What|Removed |Added
CC||rozhuk...@gmail.com
Attachment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278546
Bug ID: 278546
Summary: fdevname_r: pass partially uninitialized memory to
kernel
Product: Base System
Version: 14.0-STABLE
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278545
--- Comment #3 from Ivan Rozhuk ---
(In reply to Gleb Popov from comment #2)
I am too lazy to do all workflow for one PR in my life in this project.
https://gitlab.freedesktop.org/cairo/cairo/-/merge_requests/543
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278545
Gleb Popov changed:
What|Removed |Added
CC||arr...@freebsd.org
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278545
Ivan Rozhuk changed:
What|Removed |Added
Attachment #250172||maintainer-approval?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278545
Ivan Rozhuk changed:
What|Removed |Added
CC||rozhuk...@gmail.com
Bugzilla Automation has asked freebsd-desktop (Team)
for maintainer-feedback:
Bug 278545: graphics/cairo: fix Conditional jump or move depends on
uninitialised value(s)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278545
--- Description ---
Found by valgrind:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278545
Bug ID: 278545
Summary: graphics/cairo: fix Conditional jump or move depends
on uninitialised value(s)
Product: Ports & Packages
Version: Latest
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254593
Mateusz Piotrowski <0...@freebsd.org> changed:
What|Removed |Added
Summary|Show nanoseconds timestamp |stat:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254593
Mateusz Piotrowski <0...@freebsd.org> changed:
What|Removed |Added
Component|kern|bin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278541
Bug ID: 278541
Summary: whois returns incomplete information
Product: Base System
Version: 15.0-CURRENT
Hardware: Any
OS: Any
Status: New
Severity:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230807
--- Comment #27 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=05a95d19cb248203acdd4e069d3eedfe597c3b49
commit 05a95d19cb248203acdd4e069d3eedfe597c3b49
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278539
Bug ID: 278539
Summary: devel/cmake-core: The global property
FIND_LIBRARY_USE_LIB64_PATHS evaluates to TRUE, when
on FreeBSD lib64 isn't used
Product: Ports &
Bugzilla Automation has asked freebsd-kde (group)
for maintainer-feedback:
Bug 278539: devel/cmake-core: The global property FIND_LIBRARY_USE_LIB64_PATHS
evaluates to TRUE, when on FreeBSD lib64 isn't used
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278539
--- Description ---
This code
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278521
--- Comment #7 from Yuri Victorovich ---
(In reply to Vladimir Druzenko from comment #6)
> Check your patch - option PIPEWIRE is in OPTIONS_DEFAULT.
But the option's description says that it is for screen capture, not sound.
> KDE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278535
John F. Carr changed:
What|Removed |Added
CC||j...@mit.edu
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278521
--- Comment #6 from Vladimir Druzenko ---
1. Check your patch - option PIPEWIRE is in OPTIONS_DEFAULT.
2 and 3. Fifefox and Thunderbird have patches (in ports) with pipewire support.
4. KDE support pipewire on FreeBSD for more than year -
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278535
Bug ID: 278535
Summary: bhyve: occasional long delays during boot
Product: Base System
Version: 15.0-CURRENT
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253888
Lexi Winter changed:
What|Removed |Added
CC||lexi.free...@le-fay.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
Bjoern A. Zeeb changed:
What|Removed |Added
CC||b...@freebsd.org
--- Comment #9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278532
Bug ID: 278532
Summary: vmstat percentages wrong on 32 bit systems
Product: Base System
Version: 14.0-STABLE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278521
--- Comment #5 from Yuri Victorovich ---
The firefox port also doesn't have the pipewire support.
I suggest that the attached patch should be committed in the mean time.
Then the following items should be fixed:
1. Support PipeWire in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278448
--- Comment #4 from crb ---
Created attachment 250159
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=250159=edit
picture of vivado running
This shows the files read in as non modules files
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278448
--- Comment #3 from crb ---
I've used a read_verilog/add_files/import_files (I've tried them all) to read
in a file. Vivado, in the GUI (there is no error from the tcl shel) lists
these as non-module files. And when I try to instanciate
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278448
p...@nomadlogic.org changed:
What|Removed |Added
CC||p...@nomadlogic.org
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278521
--- Comment #4 from Yuri Victorovich ---
(In reply to Vladimir Druzenko from comment #3)
I also use FreeBSD as a sole desktop OS since late 1990s.
But today XFCE4 seems to use PulseAudio by default.
Also: the chromium port doesn't
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275255
--- Comment #15 from m...@netfence.it ---
(In reply to ml from comment #14)
P.S.
I'm wrinting here on invitation from Bjoern (he was the one saying I'm possibly
seeing this specific issue).
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275255
m...@netfence.it changed:
What|Removed |Added
CC||m...@netfence.it
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278521
--- Comment #3 from Vladimir Druzenko ---
1. I'm using FreeBSD as single OS on desktop from 2009 at home and at work and
never used pulseaudio or pipewire.
2. AFAIK pulseaudio is deprecated by upstream and superseded with pipewire. For
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278521
--- Comment #2 from Yuri Victorovich ---
(In reply to Vladimir Druzenko from comment #1)
Because most/all desktop environments use PUlseAudio by default, unless I am
mistaken.
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278063
Joel Bodenmann changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278063
Joel Bodenmann changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278521
Vladimir Druzenko changed:
What|Removed |Added
CC||v...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278200
Jason E. Hale changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278200
--- Comment #6 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=9e251d0efb9fab2729c2e777ce14fb96b13d6f35
commit 9e251d0efb9fab2729c2e777ce14fb96b13d6f35
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278200
--- Comment #5 from Jason E. Hale ---
The linking errors I was seeing were caused by the addition qtkeychain to the
qt-creator source [1] and unrelated to the version of Qt installed, but this
only happens if security/libsecret is also
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278524
--- Comment #2 from Adrian Chadd ---
ok, let's see if this is a WB225 NIC (AR9485 + AR30xx BT)
https://techinfodepot.shoutwiki.com/wiki/Atheros_AR5B225
I added btcoex support a while back but didn't enable it by default.
You need to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278529
Bug ID: 278529
Summary: WITHOUT_SENDMAIL=true WITHOUT_LPR=true installs
directories which are then deleted by delete-old
Product: Base System
Version: Unspecified
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278524
--- Comment #1 from Dmitry Lukhtionov ---
mitya@acer:/etc# ifconfig -v wlan0
wlan0: flags=8843 metric 0 mtu 1500
options=0
ether 68:94:23:7a:41:25
groups: wlan
ssid "" channel 12 (2467 MHz 11b) bssid
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278524
Bug ID: 278524
Summary: [ath] Atheros AR9462 `list scan` empty output
Product: Base System
Version: 14.0-STABLE
Hardware: amd64
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255337
--- Comment #36 from Dmitry Lukhtionov ---
(In reply to Adrian Chadd from comment #33)
I can not find any bluetooth or another stuff in `pciconf` output
mitya@acer:/etc# pciconf -l -v
hostb0@pci0:0:0:0: class=0x06 rev=0x09
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255337
--- Comment #35 from Dmitry Lukhtionov ---
(In reply to Bjoern A. Zeeb from comment #34)
root@acer:/home/mitya # ifconfig wlan0 up
oot@acer:/home/mitya # ifconfig wlan0
wlan0: flags=8843 metric 0 mtu 1500
options=0
ether
Bugzilla Automation has asked freebsd-chromium (Nobody)
for maintainer-feedback:
Bug 278521: www/chromium: Change default audio output to PULSEAUDIO to make
chromium to play nice with desktop environments
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278521
--- Description ---
Nowadays it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278521
Bug ID: 278521
Summary: www/chromium: Change default audio output to
PULSEAUDIO to make chromium to play nice with desktop
environments
Product: Ports & Packages
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262895
--- Comment #2 from Jamie Landeg-Jones ---
Thanks Gordon. Would it have been better for me to submit a review instead, or
is that just for committers?
Cheers, Jamie
--
You are receiving this mail because:
You are on the CC list for the
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278417
Dimitry Andric changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278417
--- Comment #10 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=b449894978b56651bc8d2a19b03c4af67e4ec59c
commit b449894978b56651bc8d2a19b03c4af67e4ec59c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278417
--- Comment #9 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=2dff504999f570d45e969f62a3911f5d8310ab21
commit 2dff504999f570d45e969f62a3911f5d8310ab21
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278399
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278489
--- Comment #2 from martin ---
Indeed evaltime works in that scenario.
The issue was originally shared on forums here:
https://forums.freebsd.org/threads/tracing-shared-library-functions-using-dtrace.93172/
I tried to simplified is as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260161
Stephen Hurd changed:
What|Removed |Added
CC||sh...@freebsd.org
--- Comment #7
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278319
Christos Margiolis changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278489
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278457
Guido Falsi changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|---
1 - 100 of 163589 matches
Mail list logo