Paul Eggert <eggert@cs.ucla.edu> writes:

> On 3/8/20 1:34 AM, Pieter van Oostrum wrote:
>> (gdb) p (char *)lispsym
>> $34 = 0x198 <error: Cannot access memory at address 0x198>
>> (gdb) p (char *)&lispsym[0]
>> 'lispsym' has unknown type; cast it to its declared type
>
> lispsym's type is not known?! Either your compiler or your debugger has
> got a serious bug.
>
> What does this command do?
>
> (gdb) p (char *) &lispsym

gdb) p (char *) &lispsym
$35 = 0x100a38d30 "\230\001"

By the way, the same comes up from
dsymutil   -dump-debug-map  emacs

      - { sym: _lispsym, binAddr: 0x0000000100A38D30, size: 0x00000000 }

>
> Also, what does 'objdump -g emacs.o' say about lispsym? Mine says this:
>
> emacs.o:     file format elf64-x86-64

objdump doesn't do Mach-O object files.

I did use dwarfdump which gives debug info. But it doesn't mention lispsym, although it gives other variables.