Re: GDB breakpoints are broken in new threads -- here's why

2023-04-11 Thread Samuel Thibault
Sergey Bugaev, le mar. 11 avril 2023 11:48:45 +0300, a ecrit: > On Tue, Apr 11, 2023 at 1:50 AM Samuel Thibault > wrote: > > Sergey Bugaev, le dim. 02 avril 2023 15:22:33 +0300, a ecrit: > > > I propose the following: before resetting the exception port, glibc > > > would fetch the previous one,

Re: GDB breakpoints are broken in new threads -- here's why

2023-04-11 Thread Sergey Bugaev
On Tue, Apr 11, 2023 at 1:50 AM Samuel Thibault wrote: > Sergey Bugaev, le dim. 02 avril 2023 15:22:33 +0300, a ecrit: > > I propose the following: before resetting the exception port, glibc > > would fetch the previous one, and if it's non-null, it will perform a > > special synchronous RPC on it

Re: GDB breakpoints are broken in new threads -- here's why

2023-04-10 Thread Samuel Thibault
Hello, Sergey Bugaev, le dim. 02 avril 2023 15:22:33 +0300, a ecrit: > I propose the following: before resetting the exception port, glibc > would fetch the previous one, and if it's non-null, it will perform a > special synchronous RPC on it, both passing the new exception port > that it would se

GDB breakpoints are broken in new threads -- here's why

2023-04-02 Thread Sergey Bugaev
Hello -- and pardon the clickbait-y subject line (a large part of this was written yesterday, on April 1st :) While debugging my multi-threaded translator [0], I ran into an annoying issue: when I set a breakpoint on a server-side MIG routine (S_dir_readdir in my specific case) and send the matchi