linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Buettner <kev@primenet.com>
To: Pierre Sarrazin <sarrazip@machinasapiens.com>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: Help w/ gdb
Date: Sat, 26 Feb 2000 09:23:14 -0700	[thread overview]
Message-ID: <1000226162314.ZM9153@saguaro.lan> (raw)
In-Reply-To: Pierre Sarrazin <sarrazip@machinasapiens.com> "Re: Help w/ gdb" (Feb 16,  2:11pm)


On Feb 16,  2:11pm, Pierre Sarrazin wrote:

[lots of stuff snipped]
> The program executes fine by itself, as well as in GDB without
> breakpoints.
>
> Here is the scenario.  I enter GDB and set a breakpoint on this line
> of prog.c:
>
>         (*function)();
>
> Then I run the program and GDB stops on that line. I give the "step"
> command and get this:
>
> ---------------------------------------------------------------------------
> (gdb) break 15
> Breakpoint 1 at 0x1800734: file prog.c, line 15.
> (gdb) run
> Starting program: /home/sarrazip/pgm/bug-gdb-dll/prog
>
> Breakpoint 1, main (argc=1, argv=0x7ffffbd4) at prog.c:15
> 15              (*function)();
> (gdb) step
> 0x161a61c in library_function () at libfoo.c:7
> 7       }
> (gdb) next
> This is library_function()
> --------------------------
> main (argc=1, argv=0x7ffffbd4) at prog.c:17
> 17              dlclose(handle);
> (gdb)
> ---------------------------------------------------------------------------

Pierre,

Thanks for including the program and detailed bug report.  I mentioned in
earlier email that I was merging the patches for linux/ppc gdb into the
current sourcebase.  I am happy to report that this merge is complete and
that the source may be downloaded from the sourceware site.  See

    http://sourceware.cygnus.com/gdb

for more information.  Franz Sirl has also created an RPM from sources
earlier in the week and placed it in

    ftp://devel.linuxppc.org/users/fsirl/

(I'm not sure if his sources contain my most recent shared library fixes
though.)

Anyway, when I run your program, I'm now seeing the following
(correct, I believe) output:

    GNU gdb 20000204
    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.
    There is absolutely no warranty for GDB.  Type "show warranty" for details.
    This GDB was configured as "powerpc-unknown-linux-gnu"...
    (gdb) b 15
    Breakpoint 1 at 0x1800734: file prog.c, line 15.
    (gdb) r
    Starting program: /home/kev/ctests/pierre/prog

    Breakpoint 1, main (argc=1, argv=0x7ffffd54) at prog.c:15
    15              (*function)();
    (gdb) s
    library_function () at libfoo.c:5
    5               printf("This is library_function()\n");
    (gdb) next
    This is library_function()
    6               printf("--------------------------\n");
    (gdb) next
    --------------------------
    7       }
    (gdb) next
    main (argc=1, argv=0x7ffffd54) at prog.c:17
    17              dlclose(handle);

Kevin

--
Kevin Buettner
kev@primenet.com, kevinb@redhat.com

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-02-26 16:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-16 19:11 Help w/ gdb Pierre Sarrazin
2000-02-16 19:31 ` Kevin Buettner
2000-02-26 16:23 ` Kevin Buettner [this message]
     [not found] <1000117223224.ZM16757@saguaro.lan>
2000-01-18  0:40 ` Sean Chitwood
2000-01-18  2:04   ` Kevin Buettner
  -- strict thread matches above, loose matches on Subject: below --
2000-01-16 20:41 D.J. Barrow
2000-01-15 21:36 Mac-On-Linux Mailing Lists Dan Burcaw
2000-01-16  7:12 ` Help w/ gdb Sean Chitwood
2000-01-16 16:46   ` Kevin Buettner
2000-01-17 22:02     ` Sean Chitwood
2000-02-26 16:35   ` Kevin Buettner

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=1000226162314.ZM9153@saguaro.lan \
    --to=kev@primenet.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=sarrazip@machinasapiens.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 NNTP newsgroup(s).