Timeline for How can I locate the stacks of child tasks (threads) using /proc/<pid>/maps?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 15, 2023 at 20:38 | comment | added | Eduardo Trápani | @vykt I don't know, that's an interesting question, you might want ask it (as a new one) adding the output from Firefox and Chromium. Or even better creating a small test program that opens a couple of threads. People are more inclined to answer if they can reproduce the issue on their computers. Something like the code here. | |
| Oct 15, 2023 at 10:59 | comment | added | vykt | In what case would a child task not need its own stack? Surely its .text would have to operate entirely on heap allocations, which is impossible as far as I am aware. Here is my output of your script for a chromium based browser: pastebin.com/5RRdrNbk | |
| Oct 15, 2023 at 6:04 | history | answered | Eduardo Trápani | CC BY-SA 4.0 |