bug#65268: 30.0; Clarifications needed in etc/DEBUG, section for Android

bug#65268: 30.0; Clarifications needed in etc/DEBUG, section for Android

[Johan Widén]

Note: This is a request for clarifications in emacs 30 documentation. I
submit the bug report using emacs 29.1, information about the
configuration of my current emacs, is irrelevant.

I believe a bit more info is needed: A pointer to "free Android", so
that one can find it and install it, and set it up for emacs and
debugging.

A description on how to debug startup problems that happens very early
in emacs startup, such as when a library object file is missing,
or something is corrupt in a library objects initialization.

In Android versions provided from manufacturers one has the developer
option that the app should wait for the debugger to connect, before it
starts up.
-- 
Johan Widén, tel: +46705367346
Risvägen 5 A, 192 73 Sollentuna, SWEDEN

bug#65268: 30.0; Clarifications needed in etc/DEBUG, section for Android

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Johan Widén <j.e.widen@gmail.com> writes:

> Note: This is a request for clarifications in emacs 30 documentation. I
> submit the bug report using emacs 29.1, information about the
> configuration of my current emacs, is irrelevant.
>
> I believe a bit more info is needed: A pointer to "free Android", so
> that one can find it and install it, and set it up for emacs and
> debugging.

https://replicant.us, or Google's AOSP-based emulator images.  I will
write something to that effect.

Some other versions of Android such as LineageOS also bundle gdbserver.
But we cannot recommend them, as they aren't free software.

> A description on how to debug startup problems that happens very early
> in emacs startup, such as when a library object file is missing,
> or something is corrupt in a library objects initialization.

Would you please elaborate as to what problems you're referring to here?
If a shared library or required symbol is missing, Emacs will not start
up at all, and there won't be anything to debug.

> In Android versions provided from manufacturers one has the developer
> option that the app should wait for the debugger to connect, before it
> starts up.

This is irrelevant towards debug.sh, given that it already conveys that
the system should first wait for a debugger to attach before proceeding
with program startup:

    # Exit if the activity could not be started.
    adb -s $device shell am start -D -n "$package/$activity"
                                  ^^

bug#65268: 30.0; Clarifications needed in etc/DEBUG, section for Android

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

I've expanded java/DEBUG to mention Gdbserver, and some other specifics
regarding log messages and backtraces.  Closing, thanks.

bug#65268: 30.0; Clarifications needed in etc/DEBUG, section for Android

[Johan Widén]

Looks great!

Den ons 16 aug. 2023 kl 10:14 skrev Po Lu <luangruo@yahoo.com>:
>
> I've expanded java/DEBUG to mention Gdbserver, and some other specifics
> regarding log messages and backtraces.  Closing, thanks.



-- 
Johan Widén, tel: +46705367346
Risvägen 5 A, 192 73 Sollentuna, SWEDEN