Messages in this thread |  | | Date | Mon, 21 May 2001 18:28:30 -0400 (EDT) | From | Adam <> | Subject | debugging 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/
|  |