What Does This Mean？？？

[buyifan43]

I got something saying collecting debug info on my jailbroken PW4, and it generates .tgz files and .txt logs.
I'm unable to open the website shown above.

[NiLuJe]

That's the side-effects of having to flag the device as a debug-friendly for JB purposes.

That's an internal lab126 URL.

Also:

Moderator Notice
Your image breaks the forum layout. Please review the forum guidelines.

(i.e., move it to an attachment).

[mergen3107]

@NiLuJe
Sorry for bumping a very old thread.

Do you know what process/binary/script is responsible for collecting this debug info? Can I disable it somehow?

I get cmd_, powerd_ core dump files (30 MB each) and bunch of reports every now and then. I think it is when I connect to Wi-Fi, or connect with sftp, or maybe even exit KOReader. I am worried about those writes of 30 MB over long term…

[mergen3107]

Update:

I found some hints in /usr/bin/dump-stack and created two files in /mnt/us/ :
DISABLE_CORE_DUMP and DISABLE_CORE_DUMP_ALERT

No more heavy dump files!

Only things that are created from time to time are Indexer_ files and some small html and tar.gz files.

This usually happens after Kindle UI freezes for a minute or so, after I enable Wi-Fi. I suspect that it freezes when trying to check for OTA, and I blocked OTA binaries (and otaup script). So maybe because of that

All this happened on FW 5.16.21

I’ll try to replace ota scripts with some dummy empty scripts later, so that command “will work” keeping Kindle UI happy.

[mergen3107]

Final notes and verdict.

Indexer files appeared because dump-stack called dmcc.sh in the same /usr/bin/ location.

I am not really sure why dump-stack was called at all from dump-and-kill-cvm in /usr/bin/ , because it only checks for the file /PRE_GM_DEBUGGING_FEATURES_ENABLED__REMOVE_AT_GMC (which is required to be present by the JB).

Maybe main question is why dump-and-kill-cvm is called at all. But I couldn't find it.

For now, I just did (with mntroot rw/ro around it)
ln -s -b /dev/null /usr/bin/dump-stack

and it stopped from logs and dumps appearing (no more DISABLE_CORE_DUMP files needed).

dmcc.sh says in the header that this script is intended to be present only on debug devices, not on production ones. So, I think it is safe...?

[mergen3107]

Only thing I noticed is that sftp session is now very slow. Each action (browse folders, rename, or others) takes 4-5 seconds. Even terminal with PuTTy.

[mergen3107]

@Marek
Can you please have a look at my posts above?
Do you have any comments?
Do you think, for example, this blocking of core dumping should be a part of JB?
Or do you think there is something else going on and I should investigate more?

[j.p.s]

Originally Posted by mergen3107

All this happened on FW 5.16.21

I’ll try to replace ota scripts with some dummy empty scripts later, so that command “will work” keeping Kindle UI happy.

mergen3107,

Did you ever try dummy ota scripts to simulate ota checking success?

[mergen3107]

No, OTA scripts I just blocked