https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250954
--- Comment #6 from Michał Górny ---
I'm sorry, I've confused PT_LWPINFO with PT_GETLWPLIST. I'll make the example
more clear.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197778
Greg V changed:
What|Removed |Added
CC||greg@unrelenting.technology
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250954
--- Comment #5 from Konstantin Belousov ---
(In reply to Michał Górny from comment #4)
I do not quite understand what do you mean by 'relying on LWP events'. Events
are delivered by reporting stops, there is no separate channel that
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232921
Juraj Lutter changed:
What|Removed |Added
CC||ju...@lutter.sk
--- Comment #12
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250954
--- Comment #4 from Michał Górny ---
That's just a cheap example.
So do I understand correctly that your recommendation is to call PT_LWPINFO and
update the thread list every time the debugger stops rather than relying on LWP
events to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250954
--- Comment #3 from Konstantin Belousov ---
Generally if you using PT_LWPINFO, you should use it after each reported stop.
I am not sure, in your test, which stop occurs when the thread is created,
it could be earlier than you call to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246099
Mateusz Piotrowski <0...@freebsd.org> changed:
What|Removed |Added
Status|New |Open
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=231027
Bug 231027 depends on bug 228934, which changed state.
Bug 228934 Summary: objcopy (from elftoolchain) does not set ELF OS/ABI field
for binary->ELF conversion
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228934
What
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250954
--- Comment #2 from Michał Górny ---
I can reproduce the problem using the attached program. The dr0 output for the
new thread matches g_val rather than g_val2, as set *before* new thread event
arrives.
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250954
--- Comment #1 from Michał Górny ---
Created attachment 219458
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219458=edit
Minimal demonstration program
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250954
Bug ID: 250954
Summary: ptrace(): weird ordering between inheriting debug
registers and reporting a new thread
Product: Base System
Version: 12.2-RELEASE
Hardware:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250908
Akos Somfai changed:
What|Removed |Added
CC||akos.som...@gmail.com
--- Comment
14 matches
Mail list logo
