LHC@home

... Why the debugger needs to get Foreground Window Data, I don't know.

To notice if many crashes are connected with one particular piece of software, perhaps?

But that seems like a long shot to me.

River~~

Makes sense, but I think the disadvantages in privacy are bigger than the advantages in debugging...

---

... Why the debugger needs to get Foreground Window Data, I don't know.

To notice if many crashes are connected with one particular piece of software, perhaps?

But that seems like a long shot to me.

River~~

Makes sense, but I think the disadvantages in privacy are bigger than the advantages in debugging...

Agree totally - I was trying to undertand the motive, I do not agree with it. And a proper operating system would not let tasks find out about other tasks either, in my opinion.

Wait...wait..wait...WHAT

What exactly is being sent in the debugger information?

---

Wait...wait..wait...WHAT

What exactly is being sent in the debugger information?

The traceback is sending info (among other things) about what the graphics are doing. This makes perfect sense if it thinks the LHC graphics were running at the time.

What is contentious is that within this info is not only suff about the LHC graphics task, but also info about names of other windows open on the screen at the time.

It is not looking inside the code or data of those windows, but it is reporting on the title of one of those windows.

So if it crashed while you were looking at a website which put (say) "Naughtie nudies" in the title bar, everyone who looked at the traceback sufficently carefully would know that that was the title. Could be embarrassing for some users...

If there is no title on the web page, some browsers put the url in the title bar, so that would be visible through the debugger due to the decision of the operating system and browser to place the info in a relatively public place.

R~~

And a proper operating system would not let tasks find out about other tasks either, in my opinion.

Absolutely.

---