headers
Hoefle Marco | 1 Mar 2011 09:27
Picon

AW: GDB Server for Xilinx Microblaze

Hi Michael,
Thanks for your reply.
Xilinx won't support officially any Linux related issues (I used to work in the support center and Linux
cases were the easy cases: sorry not supported)

So the Microblaze support in GDB 7.2 is for debugging standalone applications together with XMD only or
would it work together with a cross-compiled gdb server?

Embedded distributors like bluecat or petalogix have ported GDB for Linux on Microblaze but the free old
versions (at least from petalogix) had quite an old GDB + gdbserver which didn't work properly (slow and
crashes when embedding them in an eclipse environment)

So do you have any hints for me how to proceed to get a new GDB + gdbserver up?

Thanks,
Marco

-----Ursprüngliche Nachricht-----
Von: Michael Eager [mailto:eager <at> eagerm.com] 
Gesendet: Montag, 28. Februar 2011 16:40
An: Hoefle Marco
Betreff: Re: GDB Server for Xilinx Microblaze

Hoefle Marco wrote:
> Hello,
> we are using Linux running on a Xilinx Microblaze in a FPGA.
> It runs fine but we lack proper debugging (we are doing it old school
> like: printfs...),
> so modern stuff like code stepping within an eclipse cdt environment
> would be greatly appreciated :-)
(Continue reading)

Permalink | Reply | 1 comment |
headers
dpc@ucore.info | 1 Mar 2011 15:47
Gravatar

gdb + remote qemu, Ctrl-C does not work

Hi,

I have a little problem with arm-none-eabi-gdb that I'm debugging
remote qemu-system-arm targets.

The problem is: Ctrl-C does not break qemu target, but disconnects
qemu completely.

(gdb) c
Continuing.
^CRemote communication error.  Target disconnected.: Connection reset by peer.

GDB is not offering me the Ctrl-C sequence to break execution (like my
native gdb does) so I guess I should use some different options
because what I know is (I've tried), that sending SIGINT to
arm-none-eabi-gdb process does break the execution. I see no reason
Ctrl-C could not work if sending SIGINT does.

I'm using default options and here are some relevant version strings:

$ arm-none-eabi-gdb --version
GNU gdb (Sourcery G++ Lite 2010.09-51) 7.2.50.20100908-cvs
$ uname -a
Linux mutex 2.6.35-27-generic #48-Ubuntu SMP Tue Feb 22 20:25:46 UTC
2011 x86_64 GNU/Linux

Much appreciated.

Regards,
Dawid
(Continue reading)

Permalink | Reply | 14 comments |
headers
Mike Frysinger | 1 Mar 2011 19:35
Picon
Favicon
Gravatar

Re: gdb + remote qemu, Ctrl-C does not work

On Tuesday, March 01, 2011 09:47:57 dpc <at> ucore.info wrote:
> I have a little problem with arm-none-eabi-gdb that I'm debugging
> remote qemu-system-arm targets.
> 
> The problem is: Ctrl-C does not break qemu target, but disconnects
> qemu completely.
> 
> (gdb) c
> Continuing.
> ^CRemote communication error.  Target disconnected.: Connection reset by
> peer.

last i looked at this, it seemed like a qemu problem, not gdb
-mike
Permalink | Reply | 13 comments |
headers
dpc@ucore.info | 1 Mar 2011 23:52
Gravatar

Re: gdb + remote qemu, Ctrl-C does not work

On Tue, Mar 1, 2011 at 7:35 PM, Mike Frysinger <vapier <at> gentoo.org> wrote:
> On Tuesday, March 01, 2011 09:47:57 dpc <at> ucore.info wrote:
>> I have a little problem with arm-none-eabi-gdb that I'm debugging
>> remote qemu-system-arm targets.

> last i looked at this, it seemed like a qemu problem, not gdb
> -mike

Clearly the gdb has some way to break gdb if sending SIGINT to gdb
works. Any way to emulate this on Ctrl-C?

--

-- 
http://dpc.ucore.info
Permalink | Reply | 12 comments |
headers
Michael Snyder | 2 Mar 2011 00:25
Favicon

question, xmalloc and gdbserver?

What's the policy about using malloc vs. xmalloc in gdbserver?
I notice both are used, with xmalloc being favored, but there are
still quite a few calls to malloc.
Permalink | Reply | 4 comments |
headers
Nick Lewycky | 2 Mar 2011 00:42
Picon
Favicon

crash on invalid dwarf info

Hi,

I encountered a crash in GDB caused when trying to debug a program
with invalid Dwarf info. Before crashing, GDB emits a warning "Dwarf
Error: wrong version in compilation unit header (is 0, should be 2, 3,
or 4)" and dwarfdump has this to say:

  COMPILE_UNIT<header overall offset = 0>:
  <0><  218>      DW_TAG_subprogram
  dwarfdump ERROR:  ref formwith no ref?!:  DW_DLE_ATTR_FORM_OFFSET_BAD (119)

I thought, before I spend time reducing a testcase, that I should
check whether there's any interest in fixing crash on invalid bugs. I
realize that it gets cumbersome to sanity check every little thing in
elf and dwarf, so it may not be worth filing a bug for it. Thoughts?

Here's the stack trace:

Program received signal SIGSEGV, Segmentation fault.
peek_die_abbrev (info_ptr=0x800057e68bb2 <Address 0x800057e68bb2 out
of bounds>, bytes_read=0x7fffffffca6c, cu=0x7fffffffcae0) at
../../src/gdb/dwarf2read.c:4120
4120  abbrev_number = read_unsigned_leb128 (abfd, info_ptr, bytes_read);
(top) bt
#0  peek_die_abbrev (info_ptr=0x800057e68bb2 <Address 0x800057e68bb2
out of bounds>, bytes_read=0x7fffffffca6c, cu=0x7fffffffcae0) at
../../src/gdb/dwarf2read.c:4120
#1  0x00000000005a1378 in load_partial_dies (abfd=<value optimized
out>, buffer=<value optimized out>, info_ptr=0x800057e68bb2 <Address
0x800057e68bb2 out of bounds>, building_psymtab=<value optimized out>,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mike Frysinger | 2 Mar 2011 00:50
Picon
Favicon
Gravatar

Re: gdb + remote qemu, Ctrl-C does not work

On Tuesday, March 01, 2011 17:52:29 dpc <at> ucore.info wrote:
> On Tue, Mar 1, 2011 at 7:35 PM, Mike Frysinger <vapier <at> gentoo.org> wrote:
> > On Tuesday, March 01, 2011 09:47:57 dpc <at> ucore.info wrote:
> >> I have a little problem with arm-none-eabi-gdb that I'm debugging
> >> remote qemu-system-arm targets.
> > 
> > last i looked at this, it seemed like a qemu problem, not gdb
> 
> Clearly the gdb has some way to break gdb if sending SIGINT to gdb
> works.

if the remote stub does things wrong, there's nothing the gdb client should be 
doing to work around it.  fix the remote stub.
-mike
Permalink | Reply | 11 comments |
headers
santoshp | 2 Mar 2011 06:05
Picon

Re: debug core file of size 50GB using GDB in RHEL5


Thanks to all. You are true as the objdump -s does not show any symbols which
tells that the core is not usable for debugging.

Thanks,
Santosh
--

-- 
View this message in context: http://old.nabble.com/debug-core-file-of-size-50GB-using-GDB-in-RHEL5-tp31029843p31046672.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
Permalink | Reply | 3 comments |
headers
santoshp | 2 Mar 2011 06:06
Picon

Re: debug core file of size 50GB using GDB in RHEL5


typo corrected.

santoshp wrote:
> 
> Thanks to all. You are true as the objdump -d(-D) or "readelf -s" on core
> file does not show any symbols which tells that the core is not usable for
> debugging.
> 
> Thanks,
> Santosh
> 

--

-- 
View this message in context: http://old.nabble.com/debug-core-file-of-size-50GB-using-GDB-in-RHEL5-tp31029843p31046676.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
Permalink | Reply | 0 comments |
headers
dpc@ucore.info | 2 Mar 2011 08:29
Gravatar

Re: gdb + remote qemu, Ctrl-C does not work

On Wed, Mar 2, 2011 at 12:50 AM, Mike Frysinger <vapier <at> gentoo.org> wrote:
>> Clearly the gdb has some way to break gdb if sending SIGINT to gdb
>> works.
>
> if the remote stub does things wrong, there's nothing the gdb client should be
> doing to work around it.  fix the remote stub.

That's the possibility as well. Someone / I could try fix qemu sources.

However I don't understand why gdb is doing something different on
SIGINT and something different on Ctrl-C.

--

-- 
http://dpc.ucore.info
Permalink | Reply | 10 comments |

Gmane