From: Daniel Jacobowitz <drow@false.org>
To: True Sylvia <truesylvia@yahoo.co.uk>
Cc: gdb@sources.redhat.com
Subject: Re: Strange GDB behavior
Date: Mon, 26 Jul 2004 13:15:00 -0000 [thread overview]
Message-ID: <20040726125851.GA9019@nevyn.them.org> (raw)
In-Reply-To: <035101c472ee$216979c0$e90218ac@Floyd>
On Mon, Jul 26, 2004 at 02:24:05PM +0530, True Sylvia wrote:
> Hi,
>
> Am using the following flavor of GDB
>
> Current directory is /tftproot/code/
> GDB is free software and you are welcome to 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.
> GDB 4.16 (sparc-sun-solaris2.5.1 --target mips64orion-elf),
> Copyright 1996 Free Software Foundation, Inc...
> (gdb)
You may wish to try a version of GDB newer than 1996; we're not likely
to be able to give you meaningful help with version 4.16.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-07-26 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 11:34 True Sylvia
2004-07-26 11:48 ` Monika Chaddha
2004-07-26 13:15 ` Daniel Jacobowitz [this message]
2004-07-26 11:58 Arun Vishwanathan
2004-07-26 13:00 ` Monika Chaddha
2004-07-26 12:09 Atul Talesara
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=20040726125851.GA9019@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=truesylvia@yahoo.co.uk \
/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