|
8 | 8 | msgstr "" |
9 | 9 | "Project-Id-Version: Flatpak\n" |
10 | 10 | "Report-Msgid-Bugs-To: \n" |
11 | | -"POT-Creation-Date: 2025-02-18 06:55+0530\n" |
| 11 | +"POT-Creation-Date: 2025-06-30 14:59+0530\n" |
12 | 12 | "PO-Revision-Date: 2018-05-20 10:36-0400\n" |
13 | 13 | " Last-Translator: Copied by Zanata <[email protected]>\n" |
14 | 14 | "Language: de\n" |
@@ -170,126 +170,166 @@ msgstr "" |
170 | 170 | msgid "Using other debugging tools" |
171 | 171 | msgstr "" |
172 | 172 |
|
173 | | -#: ../../debugging.rst:118 |
| 173 | +#: ../../debugging.rst:119 |
174 | 174 | msgid "" |
175 | 175 | "``org.freedesktop.Sdk`` also includes other debugging tools like " |
176 | 176 | "`Valgrind <https://valgrind.org/>`_ which is useful to find memory leaks." |
177 | 177 | " Once inside the :ref:`debugging:Debug shell`, it can be run with::" |
178 | 178 | msgstr "" |
179 | 179 |
|
180 | | -#: ../../debugging.rst:124 |
| 180 | +#: ../../debugging.rst:125 |
181 | 181 | msgid "" |
182 | 182 | "`Strace <https://strace.io/>`_ can be useful to check what an application" |
183 | 183 | " is doing. For example, to trace ``openat(), read()`` calls::" |
184 | 184 | msgstr "" |
185 | 185 |
|
186 | | -#: ../../debugging.rst:129 |
| 186 | +#: ../../debugging.rst:130 |
187 | 187 | msgid "" |
188 | 188 | "`Perf <https://perfwiki.github.io/main/>`_ requires access to " |
189 | 189 | "``--filesystem=/sys`` to run::" |
190 | 190 | msgstr "" |
191 | 191 |
|
192 | | -#: ../../debugging.rst:135 |
| 192 | +#: ../../debugging.rst:136 |
| 193 | +msgid "Multiple Debug shells in one sandbox" |
| 194 | +msgstr "" |
| 195 | + |
| 196 | +#: ../../debugging.rst:138 |
| 197 | +msgid "" |
| 198 | +"Sometimes it can be helpful to have multiple debugging shells at a time " |
| 199 | +"in the same sandox. For example, some debugging commands such as `dotnet-" |
| 200 | +"dump <https://learn.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-" |
| 201 | +"dump>`_ expect to be given an identifier for a running process that it " |
| 202 | +"will connect to for debugging. This essentially requires multiple " |
| 203 | +"instances of the :ref:`debugging:Debug shell`, one to run the app, and " |
| 204 | +"one for running the debugging tool." |
| 205 | +msgstr "" |
| 206 | + |
| 207 | +#: ../../debugging.rst:146 |
| 208 | +msgid "" |
| 209 | +"To accomplish this, locate either the instance or process ID of an " |
| 210 | +"existing debug shell with::" |
| 211 | +msgstr "" |
| 212 | + |
| 213 | +#: ../../debugging.rst:151 |
| 214 | +msgid "Then you can enter this same sandbox from a new terminal window using::" |
| 215 | +msgstr "" |
| 216 | + |
| 217 | +#: ../../debugging.rst:155 |
| 218 | +msgid "" |
| 219 | +"Note that this second shell likely will not be configured identically to " |
| 220 | +"the original debug shell (for example it will likely have different " |
| 221 | +"environment variables such as PATH)." |
| 222 | +msgstr "" |
| 223 | + |
| 224 | +#: ../../debugging.rst:159 |
| 225 | +msgid "" |
| 226 | +"You can verify whether both the shells are indeed in the same sandbox by " |
| 227 | +"checking the namespaces visible in each debug shell and verifying that " |
| 228 | +"they are the same. The easiest way to do this is to list the visible " |
| 229 | +"namespaces using::" |
| 230 | +msgstr "" |
| 231 | + |
| 232 | +#: ../../debugging.rst:167 |
193 | 233 | msgid "Creating a Debug extension" |
194 | 234 | msgstr "" |
195 | 235 |
|
196 | | -#: ../../debugging.rst:137 |
| 236 | +#: ../../debugging.rst:169 |
197 | 237 | msgid "" |
198 | 238 | "Like many other packaging systems, Flatpak separates bulky debug " |
199 | 239 | "information from regular content and ships it separately, in a Debug " |
200 | 240 | "extension." |
201 | 241 | msgstr "" |
202 | 242 |
|
203 | | -#: ../../debugging.rst:140 |
| 243 | +#: ../../debugging.rst:172 |
204 | 244 | msgid "" |
205 | 245 | "When an application is built, ``flatpak-builder`` automatically creates a" |
206 | 246 | " Debug extension. This can be disabled with the ``no-debuginfo`` option." |
207 | 247 | msgstr "" |
208 | 248 |
|
209 | | -#: ../../debugging.rst:144 |
| 249 | +#: ../../debugging.rst:176 |
210 | 250 | msgid "" |
211 | 251 | "To install the Debug extension created locally, pass ``--install`` to " |
212 | 252 | "``flatpak-builder`` which will set up a new remote for the build. The " |
213 | 253 | "remotes available can be checked with::" |
214 | 254 | msgstr "" |
215 | 255 |
|
216 | | -#: ../../debugging.rst:150 |
| 256 | +#: ../../debugging.rst:182 |
217 | 257 | msgid "Then install the Debug extension from that remote::" |
218 | 258 | msgstr "" |
219 | 259 |
|
220 | | -#: ../../debugging.rst:155 |
| 260 | +#: ../../debugging.rst:187 |
221 | 261 | msgid "Overriding sandbox permissions" |
222 | 262 | msgstr "" |
223 | 263 |
|
224 | | -#: ../../debugging.rst:157 |
| 264 | +#: ../../debugging.rst:189 |
225 | 265 | msgid "" |
226 | 266 | "It is sometimes useful to have extra permissions in a sandbox when " |
227 | 267 | "debugging. This can be achieved using the various sandbox options that " |
228 | 268 | "are accepted by the run command. For example::" |
229 | 269 | msgstr "" |
230 | 270 |
|
231 | | -#: ../../debugging.rst:163 |
| 271 | +#: ../../debugging.rst:195 |
232 | 272 | msgid "" |
233 | 273 | "This command runs a shell in the sandbox for the given application, " |
234 | 274 | "granting it system bus access to the bus name owned by logind." |
235 | 275 | msgstr "" |
236 | 276 |
|
237 | | -#: ../../debugging.rst:167 |
| 277 | +#: ../../debugging.rst:199 |
238 | 278 | msgid "Inspecting portal permissions" |
239 | 279 | msgstr "" |
240 | 280 |
|
241 | | -#: ../../debugging.rst:169 |
| 281 | +#: ../../debugging.rst:201 |
242 | 282 | msgid "" |
243 | 283 | "Flatpak has a number of commands that allow to manage portal permissions " |
244 | 284 | "for applications." |
245 | 285 | msgstr "" |
246 | 286 |
|
247 | | -#: ../../debugging.rst:172 |
| 287 | +#: ../../debugging.rst:204 |
248 | 288 | msgid "To see all portal permissions of an application, use::" |
249 | 289 | msgstr "" |
250 | 290 |
|
251 | | -#: ../../debugging.rst:176 |
| 291 | +#: ../../debugging.rst:208 |
252 | 292 | msgid "To reset all portal permissions of an application, use::" |
253 | 293 | msgstr "" |
254 | 294 |
|
255 | | -#: ../../debugging.rst:182 |
| 295 | +#: ../../debugging.rst:214 |
256 | 296 | msgid "Interacting with running sandboxes" |
257 | 297 | msgstr "" |
258 | 298 |
|
259 | | -#: ../../debugging.rst:184 |
| 299 | +#: ../../debugging.rst:216 |
260 | 300 | msgid "" |
261 | 301 | "You can see all the apps that are currently running in Flatpak sandboxes " |
262 | 302 | "(since 1.2)::" |
263 | 303 | msgstr "" |
264 | 304 |
|
265 | | -#: ../../debugging.rst:189 |
| 305 | +#: ../../debugging.rst:221 |
266 | 306 | msgid "And, if you need to, you can terminate one by force (since 1.2)::" |
267 | 307 | msgstr "" |
268 | 308 |
|
269 | | -#: ../../debugging.rst:194 |
| 309 | +#: ../../debugging.rst:226 |
270 | 310 | msgid "Audit session or system bus traffic" |
271 | 311 | msgstr "" |
272 | 312 |
|
273 | | -#: ../../debugging.rst:196 |
| 313 | +#: ../../debugging.rst:228 |
274 | 314 | msgid "" |
275 | 315 | "A ``--socket=session-bus`` or a ``--socket=system-bus`` permission must " |
276 | 316 | "not be present for the logging to work." |
277 | 317 | msgstr "" |
278 | 318 |
|
279 | | -#: ../../debugging.rst:199 |
| 319 | +#: ../../debugging.rst:231 |
280 | 320 | msgid "" |
281 | 321 | "Session bus traffic can be audited by passing ``--log-session-bus`` to " |
282 | 322 | "``flatpak run``::" |
283 | 323 | msgstr "" |
284 | 324 |
|
285 | | -#: ../../debugging.rst:204 |
| 325 | +#: ../../debugging.rst:236 |
286 | 326 | msgid "" |
287 | 327 | "This can be useful to figure out the bus names used by an application and" |
288 | 328 | " the corresponding ``--talk-name`` or ``--own-name`` permissions " |
289 | 329 | "required::" |
290 | 330 | msgstr "" |
291 | 331 |
|
292 | | -#: ../../debugging.rst:210 |
| 332 | +#: ../../debugging.rst:242 |
293 | 333 | msgid "" |
294 | 334 | "Similarly, system bus traffic can be audited by passing ``--log-system-" |
295 | 335 | "bus`` to ``flatpak run``. This also requires a system bus name to be " |
|
0 commit comments