From: Sinisa Milivojevic <sinisa@mysql.com>
To: ac131313@cygnus.com
Cc: gdb@sources.redhat.com, gdb-testers@sources.redhat.com
Subject: Re: GDB 5.0.92 available
Date: Wed, 31 Oct 2001 05:21:00 -0000 [thread overview]
Message-ID: <15327.64458.494145.962156@sinisa.nasamreza.org> (raw)
In-Reply-To: <3BDF7F79.6050205@cygnus.com>
Andrew Cagney writes:
> (finally)
>
> GDB 9.0.92 is available for download. See:
>
> ftp://sources.redhat.com/pub/gdb/snapshots/
>
> Andrew
>
A short list of fixes / improvements ??
Anyway, may be you can answer my question on .gdbinit.
Prior versions (4.*) of gdb would read local .gdbinit files too, not
just .gdbinit in your HOME dir. So, for each project you could have a
separate .gdbinit located in the directory of the executables.
I have tried several snapshots and none of them will read any init
file except the one in the HOME.
Is there a workaround ??
--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic <sinisa@mysql.com>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com
next prev parent reply other threads:[~2001-10-31 5:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 20:35 Andrew Cagney
2001-10-31 5:21 ` Sinisa Milivojevic [this message]
2001-10-31 14:23 ` Andrew Cagney
2001-10-31 8:09 ` Old bug with 'gdb/dbxread.c' and screwed up MIPS symbolic debugging Steven J. Hill
2001-10-31 8:32 ` Daniel Jacobowitz
2001-10-31 11:12 ` Andrew Cagney
2001-10-31 14:47 ` Stabs and discarded functions (was Re: Old bug with 'gdb/dbxread.c' and screwed up MIPS symbolic debugging...) Daniel Jacobowitz
2001-10-31 8:14 ` GDB 5.0.92 available Trond Eivind Glomsrød
2001-10-31 9:15 ` Wai-Sun Chia
2001-10-31 10:51 ` Fernando Nasser
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=15327.64458.494145.962156@sinisa.nasamreza.org \
--to=sinisa@mysql.com \
--cc=ac131313@cygnus.com \
--cc=gdb-testers@sources.redhat.com \
--cc=gdb@sources.redhat.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