Re: [BUG] phantom newlines while moving headings [9.6-pre ( @ /home/chomwitt/.config/emacs/elpa/org-9.6pre0.20221110.85807/)]

[Ihor Radchenko <yantar92@posteo.net>]

[-- Attachment #1: Type: text/plain, Size: 424 bytes --]

chomwitt@posteo.eu writes:

> It follows a possible org chunk that reproduce the phantom newlines that
> are created while trying to move a headline from a state where there
> are no newlines between the headers.

Could you please provide more information?
Which headline should I move to reproduce the problem?

I tried to move headlines randomly in the attached file (your example)
but I do not see any newlines created.


[-- Attachment #2: bug2.org --]
[-- Type: application/vnd.lotus-organizer, Size: 3113 bytes --]

* Linux system programming

** What is a product  Standard  ?
  :posix:sus: <<lsb>> 

*** Unix characteristics

**** Portability

One 

*** Standard Makefile Targets

** Headers

How to find the include paths used by the gcc compiler ?

...

** Keyboard 

     A scancode is the lowest identification number for a key, 

evtest - Input device event monitor and query tool

*** Extra keyboard keys

Many
** Time
*** Check current time-date-timezone

n
** References/Example_code

*** TLPI book's code (The Linux Programming Interface)

**** DONE TOsDO Socket stream example
     CLOSED: [2017-01-11 Τετ 06:29]

Sockets

$ gcc -g -o us_xfr_cl us_xfr_cl.c  -L../lib -I../lib/
../lib/error_functions.o $ gcc -g -o us_xfr_sv  us_xfr_sv.c  -L../lib
-I../lib/ ../lib/error_functions.o

http://man7.org/tlpi/

** Utilities

*** strace 

strace traces and logs  all system calls issued by a program along with
their return codes. In this way, you can watch how a program interacts
with the system, which is useful for tracking down behavioural issues.
ss

strace -c foo_obj   // generate stats of syscalls

*** pmap 

$ foo &
[pid]
$ pmap pid

*** objdump

objdump is a program for displaying various information about object
files. For instance, it can be used as a disassembler to view an
executable in assembly form. It is part of the GNU Binutils for
fine-grained control over executables and other binary data.

$ objdump -f foo_obj   // see information related to the overall file
header , like file format

$ objdump -h foo_ob    // Dumping the section headers from the ELF
executable // If the ELF executable contains debug symbols will contain 
		       // section  with names beginning with .debug_ -
these are // ldthe DWARF debugging sections

26 .debug_aranges 00000020  00000000  00000000  00001037
		 CONTENTS, READONLY, DEBUGGING
27 .debug_pubnames 00000028  00000000  00000000  00001057
		 CONTENTS, READONLY, DEBUGGING
28 .debug_info   000000cc  00000000  00000000  0000107f
		 CONTENTS, READONLY, DEBUGGING
29 .debug_abbrev 0000008a  00000000  00000000  0000114b
		 CONTENTS, READONLY, DEBUGGING
30 .debug_line   0000006b  00000000  00000000  000011d5
		 CONTENTS, READONLY, DEBUGGING
31 .debug_frame  00000044  00000000  00000000  00001240
		 CONTENTS, READONLY, DEBUGGING
32 .debug_str    000000ae  00000000  00000000  00001284
		 CONTENTS, READONLY, DEBUGGING
33 .debug_loc    00000058  00000000  00000000  00001332
		 CONTENTS, READONLY, DEBUGGING

The first number seen for each section here is its size, and the last
is the offset where it begins in the ELF file. The debugger uses this
information to read the section from the executable

$ objdump --dwarf=info foo_obj   // display the DWARF debug_info section
//This is why DWARF encodes a full mapping between lines in the C
source code //and machine code addresses in the executable. This
information is contained in //the .debug_line section and can be
extracted in a readable form as follows:

$ objdump --dwarf=decodedline  foo_obj   // display 

http://eli.thegreenplace.net/2011/02/07/how-debuggers-work-part-3-debugging-information/

[-- Attachment #3: Type: text/plain, Size: 224 bytes --]


-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>