[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/etc/DEBUG
From: |
Nick Roberts |
Subject: |
[Emacs-diffs] Changes to emacs/etc/DEBUG |
Date: |
Tue, 14 Dec 2004 20:49:36 -0500 |
Index: emacs/etc/DEBUG
diff -c emacs/etc/DEBUG:1.28 emacs/etc/DEBUG:1.29
*** emacs/etc/DEBUG:1.28 Mon Oct 4 13:37:01 2004
--- emacs/etc/DEBUG Wed Dec 15 01:27:48 2004
***************
*** 107,142 ****
Even with a live process, these x... commands are useful for
examining the fields in a buffer, window, process, frame or marker.
Here's an example using concepts explained in the node "Value History"
! of the GDB manual to print the variable frame from this line in
! xmenu.c:
!
! buf.frame_or_window = frame;
!
! First, use these commands:
cd src
gdb emacs
! b xmenu.c:1296
r -q
! Then type C-x 5 2 to create a new frame, and it hits the breakpoint:
(gdb) p frame
! $1 = 1077872640
(gdb) xtype
Lisp_Vectorlike
PVEC_FRAME
(gdb) xframe
! $2 = (struct frame *) 0x3f0800
(gdb) p *$
$3 = {
! size = 536871989,
! next = 0x366240,
! name = 809661752,
[...]
}
(gdb) p $3->name
! $4 = 809661752
Now we can use `pr' to print the name of the frame:
--- 107,138 ----
Even with a live process, these x... commands are useful for
examining the fields in a buffer, window, process, frame or marker.
Here's an example using concepts explained in the node "Value History"
! of the GDB manual to print values associated with the variable
! called frame. First, use these commands:
cd src
gdb emacs
! b set_frame_buffer_list
r -q
! Then when Emacs it hits the breakpoint:
(gdb) p frame
! $1 = 139854428
(gdb) xtype
Lisp_Vectorlike
PVEC_FRAME
(gdb) xframe
! $2 = (struct frame *) 0x8560258
(gdb) p *$
$3 = {
! size = 1073742931,
! next = 0x85dfe58,
! name = 140615219,
[...]
}
(gdb) p $3->name
! $4 = 140615219
Now we can use `pr' to print the name of the frame:
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] Changes to emacs/etc/DEBUG,
Nick Roberts <=