search

Pernosco / pernosco

General-purpose public wiki and issue tracking
12 stars 0 forks source link

GDB window ending up in `syscall_traced` #51

Closed mgaudet closed 2 years ago

mgaudet commented 2 years ago

👋 I've got a trace where frequently when I jump to another point in the trace by clicking (eg, in the notebook), the gdb terminal loses sync and says we're in 

0x0000000070000002 in syscall_traced ()

Restarting the GDB window has worked reliably for me.

khuey commented 2 years ago

When you're clicking around are you jumping processes? The gdb panel is fixed to a particular process, and that process might be in futex_wait or similar while the other process is running?

mgaudet commented 2 years ago

Oh, almost certainly yes -- I was hunting for a particular call (I should open a new issue about conditional execution)

Perhaps a message indicating that the shell is tied to a process when jumping outside the bounds would help.

khuey commented 2 years ago

(I should open a new issue about conditional execution)

Please do.

khuey commented 2 years ago

Going forward we will display this.

image

mgaudet commented 2 years ago

That’s perfect! Informative and actionable!