From: Luis Machado <luis.machado@linaro.org>
To: Devansh Chowdhury <devanshchowdhury@gmail.com>, bug-gdb@gnu.org
Subject: Re: Reporting a bug
Date: Tue, 25 Feb 2020 13:49:00 -0000 [thread overview]
Message-ID: <3f152a79-52df-8ce2-1846-1fb9a4e37b7c@linaro.org> (raw)
In-Reply-To: <CAKT9frB_8naKmyEsSEJZq1aEDALQef-GOdZXB5ZLqTR-Kgmjwg@mail.gmail.com>
If you have a reproducer to get GDB to run into that particular error,
you can file a bug in GDB's bugzilla: https://sourceware.org/bugzilla/
On 2/21/20 6:07 PM, Devansh Chowdhury wrote:
> my log shows this message.
> I have been using the program for months and first time this problem has
> been encountered.
> internal-error: virtual memory exhausted.
> [debug]A problem internal to GDB has been detected,
> [debug]further debugging may prove unreliable.
> [debug]This is a bug, please report it.
>
prev parent reply other threads:[~2020-02-25 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 21:07 Devansh Chowdhury
2020-02-25 13:49 ` Luis Machado [this message]
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=3f152a79-52df-8ce2-1846-1fb9a4e37b7c@linaro.org \
--to=luis.machado@linaro.org \
--cc=bug-gdb@gnu.org \
--cc=devanshchowdhury@gmail.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