public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: lunn@ma.tech.ascom.ch (Andrew Lunn)
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] No stack frames in gdb
Date: Thu, 06 May 1999 00:17:00 -0000	[thread overview]
Message-ID: <199905060717.JAA09552@biferten.ma.tech.ascom.ch> (raw)

I've a problem with gdb. It does not show the stack frames. It can
tell you what function you are in, but not what function calls are
nested to get where you are.

bash-2.02$ ppcgdb mtest.exe
GNU gdb 4.17-ecosSWtools-981021
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.  This version of GDB is supported
for customers of Cygnus Solutions.  Type "show warranty" for details.
This GDB was configured as "--host=i586-cygwin32 --target=powerpc-eabi"...
(gdb) psim
Size of register r0 (0) incorrect (1 instead of 4))Connected to the simulator.
Breakpoint 1 at 0x83868: file //d/cygnus/ecos-1.1/packages/infra/v1_1/src/buffer.
cxx, line 707.
(gdb) break main
Breakpoint 2 at 0x80324: file mtest.c, line 14.
(gdb) run
Starting program: /h/aplett/mbuf/mtest.exe

Breakpoint 2, main () at mtest.c:14
14        mbinit();
(gdb) s
mbinit () at upic_mbuf.c:64
64              mmbfree = NULL; mclfree = NULL;
(gdb) s
65              m_mballoc(NMB_INIT);
(gdb) s
m_mballoc (nmb=128) at upic_mbuf.c:82
82              nbytes = (nmb * MSIZE);
(gdb) where
#0  m_mballoc (nmb=128) at upic_mbuf.c:82
(gdb)

Here i am three functions deep, but it only shows the current
function. Do i need to turn on some configuration option so that stack
frame GBD understands are be used?

	Thanks
		Andrew

             reply	other threads:[~1999-05-06  0:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-06  0:17 Andrew Lunn [this message]
1999-05-06  0:29 ` Jesper Skov
1999-05-06  0:33 ` Brendan Simon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199905060717.JAA09552@biferten.ma.tech.ascom.ch \
    --to=lunn@ma.tech.ascom.ch \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).