lkml.org 
[lkml]   [2001]   [May]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectdebugging xterm.

I'm trying to debug xterm and it seems like it is just not my day (I
suppose the "Abandon All Hope, Ye Who Enter Here" in the README for xterm
is for a reason there after all :P )

I running gdb on xterm. I'm running it as root, the current execution is
at main.c:main() and gdb seems to get lost when calling getuid), any idea?
Is there something special about getuid() I'm missing?

(gdb) next
1612 uid_t ruid = getuid();
2: screen->respond = 1448543468
1: screen = (TScreen *) 0x4000ae60
(gdb) next
1613 gid_t rgid = getgid();
2: screen->respond = Cannot access memory at address 0x4
Disabling display 2 to avoid infinite recursion.
(gdb)

it does not know where screen data structure is anymore..



--
Adam
http://www.eax.com The Supreme Headquarters of the 32 bit registers



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:53    [W:0.059 / U:0.492 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site