State of Zaphod dual screen support

Pat Kane pekane52 at
Wed Mar 3 05:29:55 PST 2010

the 2nd link should be:
you might find this part useful:

5. Without module support gdb is  not able to print the function where
   an error occurred in a module.

     If you get a line like:

   (gdb) bt
   #0  0x823b4f5 in ?? ()

   You may obtain the function the address belongs to by calling

   (gdb) call LoaderPrintSymbol(0x823b4f5)

   The symbol  returned might not always  be the name  of the function
   which contains the address. In  case of static functions the symbol
   is not known to  the loader. However LoaderPrintSymbol() will print
   the nearest known  function and the offset from  its start. You may
   easily find the exact location of the address if you do:

   # objdump --disassemble <file>.o

   <file>.o is the name of the object file containing the symbol printed.

On Wed, Mar 3, 2010 at 7:03 AM, Pat Kane <pekane52 at> wrote:
> Dave,
> For X server gdb help take a look at:
> the second is a bit out of date but still useful.
> Pat
> ---
> On Wed, Mar 3, 2010 at 12:24 AM, David Mohr <damailings at> wrote:
>  ...
>> I don't have much experience with how gdb behaves if there are no
>> debugging symbols available in _part_ of the program. Could it be that
>> I can inspect the X server by setting a breakpoint somewhere and then
>> continuing?
>> If so, what would be a good place to put a breakpoint (I have no clue
>> about X internals)?
> ...

More information about the xorg mailing list