My Personal WeeChat Cheat Sheet
You need at least WeeChat 3.2-dev
Frame pointer omission does make debugging significantly harder. Local variables are harder to locate and stack traces are much harder to reconstruct without a frame pointer to help out. Also, accessing parameters can get more expensive since they are far away from the top of the stack and may require more expensive addressing modes.
-fno-omit-frame-pointer option direct the compiler to generate code that maintains and uses stack frame pointer for all functions so that a debugger can still produce a stack backtrace even with optimizations flags.
Irrespective if you use the flag, not every function needs a frame pointer in the first place, so you can't always expect a difference with the flag.
Also, whether the function has a frame pointer is an implementation detail. Compilers can differ in implementation details (and usually they do).
|# bash generate random alphanumeric string|
|# bash generate random 32 character alphanumeric string (upper and lowercase) and|
|NEW_UUID=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1)|
|# bash generate random 32 character alphanumeric string (lowercase only)|
|cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1|
|$ telnet-ssl -z ssl imap.gmail.com 993|
|Connected to gmail-imap.l.google.com.|
|Escape character is '^]'.|
|* OK Gimap ready for requests from 22.214.171.124 z8mb75199760ljk|
|a1 LOGIN firstname.lastname@example.org my-password-here|
|* CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE ENABLE MOVE CONDSTORE ESEARCH UTF8=ACCEPT LIST-EXTENDED LIST-STATUS LITERAL- SPECIAL-USE APPENDLIMIT=35651584|
|a1 OK email@example.com authenticated (Success)|
|a2 LIST "" "*"|
|* LIST (\HasNoChildren) "/" "INBOX"|