* Using cross compiled GDB under Emacs
@ 2005-10-06 1:40 Dmytro Bablinyuk
2005-10-06 2:14 ` Dmytro Bablinyuk
0 siblings, 1 reply; 3+ messages in thread
From: Dmytro Bablinyuk @ 2005-10-06 1:40 UTC (permalink / raw)
To: gdb
I have cross compiled gdb and I can set a break point under emacs using
'C-x space' but when gdb stops at breakpoint Emacs does not show the
line where gdb stopped. If I use 'b' command - the same, Emacs does not
show the file and line where it stopped. If I try to see line info it
says that no line number available.
Here is dump:
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i386-pc-linux-gnu
--target=powerpc-linux-uclibc"...0xfff00100 in ?? ()
(gdb) ram
add symbol table from file "u-boot" at
.text_addr = 0x3fc7000
(gdb) b board_init_r
Breakpoint 1 at 0x3fcba28: file board.c, line 588.
(gdb) c
Continuing.
Breakpoint 1, <signal handler called>
(gdb) info line
No line number information available.
(gdb)
Does anybody know how to 'attach' emacs to gdb?
The program was compiled with these options
-ggdb -Os -fPIC -ffixed-r14 -meabi -D__KERNEL__
-DTEXT_BASE=0xFFF00000 -fno-builtin -ffreestanding -nostdinc -isystem
-pipe -DCONFIG_PPC -D__powerpc__ -DCONFIG_8260 -DCONFIG_CPM2 -ffixed-r2
-ffixed-r29 -mstring -mcpu=603e -mmultiple -Wall -Wstrict-prototypes
Thank you
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Using cross compiled GDB under Emacs
2005-10-06 1:40 Using cross compiled GDB under Emacs Dmytro Bablinyuk
@ 2005-10-06 2:14 ` Dmytro Bablinyuk
2005-10-06 2:16 ` Daniel Jacobowitz
0 siblings, 1 reply; 3+ messages in thread
From: Dmytro Bablinyuk @ 2005-10-06 2:14 UTC (permalink / raw)
To: gdb
> Does anybody know how to 'attach' emacs to gdb?
> The program was compiled with these options
> -ggdb -Os -fPIC -ffixed-r14 -meabi -D__KERNEL__
> -DTEXT_BASE=0xFFF00000 -fno-builtin -ffreestanding -nostdinc -isystem
> -pipe -DCONFIG_PPC -D__powerpc__ -DCONFIG_8260 -DCONFIG_CPM2 -ffixed-r2
> -ffixed-r29 -mstring -mcpu=603e -mmultiple -Wall -Wstrict-prototypes
Also the problem is with 's' and 'n' commands.
If I type
(gdb) s
it will never stop and will simply keep going until I reset JTAG.
(gdb) s
Program received signal 0, Signal 0.
<signal handler called>
(gdb) info line *(0x03fcbae8)
Line 626 of "board.c" starts at address 0x3fcbae0 <board_init_r+184> and
ends at 0x3fcbaec <board_init_r+196>.
(gdb)
The GDB version 6.3
I would be very grateful for advice
Thank you
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Using cross compiled GDB under Emacs
2005-10-06 2:14 ` Dmytro Bablinyuk
@ 2005-10-06 2:16 ` Daniel Jacobowitz
0 siblings, 0 replies; 3+ messages in thread
From: Daniel Jacobowitz @ 2005-10-06 2:16 UTC (permalink / raw)
To: Dmytro Bablinyuk; +Cc: gdb
On Thu, Oct 06, 2005 at 12:14:55PM +1000, Dmytro Bablinyuk wrote:
>
> >Does anybody know how to 'attach' emacs to gdb?
> >The program was compiled with these options
> >-ggdb -Os -fPIC -ffixed-r14 -meabi -D__KERNEL__
> >-DTEXT_BASE=0xFFF00000 -fno-builtin -ffreestanding -nostdinc -isystem
> >-pipe -DCONFIG_PPC -D__powerpc__ -DCONFIG_8260 -DCONFIG_CPM2 -ffixed-r2
> >-ffixed-r29 -mstring -mcpu=603e -mmultiple -Wall -Wstrict-prototypes
> Also the problem is with 's' and 'n' commands.
> If I type
> (gdb) s
> it will never stop and will simply keep going until I reset JTAG.
>
> (gdb) s
>
> Program received signal 0, Signal 0.
> <signal handler called>
This looks like your remote debugging stub/setup is just broken. GDB
should not be detecting either signal 0, or signal handlers.
--
Daniel Jacobowitz
CodeSourcery, LLC
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-10-06 2:16 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-10-06 1:40 Using cross compiled GDB under Emacs Dmytro Bablinyuk
2005-10-06 2:14 ` Dmytro Bablinyuk
2005-10-06 2:16 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).