public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted
@ 2024-04-10 18:33 N1nEmAn at proton dot me
2024-04-10 18:35 ` [Bug gdb/31631] " N1nEmAn at proton dot me
` (18 more replies)
0 siblings, 19 replies; 20+ messages in thread
From: N1nEmAn at proton dot me @ 2024-04-10 18:33 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
Bug ID: 31631
Summary: just run gdb and source the poc can make the memory
corrupt/exhausted
Product: gdb
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: N1nEmAn at proton dot me
Target Milestone: ---
for the details, read this report
thanks
https://github.com/N1nEmAn/wp/
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug gdb/31631] just run gdb and source the poc can make the memory corrupt/exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
@ 2024-04-10 18:35 ` N1nEmAn at proton dot me
2024-04-10 20:04 ` vries at gcc dot gnu.org
` (17 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: N1nEmAn at proton dot me @ 2024-04-10 18:35 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
N1nEmAn <N1nEmAn at proton dot me> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |N1nEmAn at proton dot me
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug gdb/31631] just run gdb and source the poc can make the memory corrupt/exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
2024-04-10 18:35 ` [Bug gdb/31631] " N1nEmAn at proton dot me
@ 2024-04-10 20:04 ` vries at gcc dot gnu.org
2024-04-10 20:04 ` [Bug python/31631] " vries at gcc dot gnu.org
` (16 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: vries at gcc dot gnu.org @ 2024-04-10 20:04 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vries at gcc dot gnu.org
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
So, we do:
...
import gdb
gdb.selected_inferior().read_memory(0, 18446744073709551615)
...
and get a virtual memory exhausted error.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] just run gdb and source the poc can make the memory corrupt/exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
2024-04-10 18:35 ` [Bug gdb/31631] " N1nEmAn at proton dot me
2024-04-10 20:04 ` vries at gcc dot gnu.org
@ 2024-04-10 20:04 ` vries at gcc dot gnu.org
2024-04-11 0:05 ` N1nEmAn at proton dot me
` (15 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: vries at gcc dot gnu.org @ 2024-04-10 20:04 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|gdb |python
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] just run gdb and source the poc can make the memory corrupt/exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (2 preceding siblings ...)
2024-04-10 20:04 ` [Bug python/31631] " vries at gcc dot gnu.org
@ 2024-04-11 0:05 ` N1nEmAn at proton dot me
2024-04-11 1:48 ` N1nEmAn at proton dot me
` (14 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: N1nEmAn at proton dot me @ 2024-04-11 0:05 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
--- Comment #2 from N1nEmAn <N1nEmAn at proton dot me> ---
i love u man. I am a college student, and this is the first binary
vulnerability in my life that has been recognized.
-------- Original Message --------
2024/4/11 上午4:04,vries at gcc dot gnu.org
<sourceware-bugzilla@sourceware.org>,来信:
> https://sourceware.org/bugzilla/show_bug.cgi?id=31631
>
> Tom de Vries <vries at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |vries at gcc dot gnu.org
>
> --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
> So, we do:
> ...
> import gdb
> gdb.selected_inferior().read_memory(0, 18446744073709551615)
> ...
> and get a virtual memory exhausted error.
>
> --
> You are receiving this mail because:
> You reported the bug.
> You are on the CC list for the bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] just run gdb and source the poc can make the memory corrupt/exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (3 preceding siblings ...)
2024-04-11 0:05 ` N1nEmAn at proton dot me
@ 2024-04-11 1:48 ` N1nEmAn at proton dot me
2024-04-11 2:51 ` N1nEmAn at proton dot me
` (13 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: N1nEmAn at proton dot me @ 2024-04-11 1:48 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
--- Comment #3 from N1nEmAn <N1nEmAn at proton dot me> ---
(In reply to Tom de Vries from comment #1)
> So, we do:
> ...
> import gdb
> gdb.selected_inferior().read_memory(0, 18446744073709551615)
> ...
> and get a virtual memory exhausted error.
i think we can fix the python code of gdb, and add a check for the number if
valid.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] just run gdb and source the poc can make the memory corrupt/exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (4 preceding siblings ...)
2024-04-11 1:48 ` N1nEmAn at proton dot me
@ 2024-04-11 2:51 ` N1nEmAn at proton dot me
2024-04-11 10:53 ` vries at gcc dot gnu.org
` (12 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: N1nEmAn at proton dot me @ 2024-04-11 2:51 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
--- Comment #4 from N1nEmAn <N1nEmAn at proton dot me> ---
Created attachment 15459
--> https://sourceware.org/bugzilla/attachment.cgi?id=15459&action=edit
poc
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] just run gdb and source the poc can make the memory corrupt/exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (5 preceding siblings ...)
2024-04-11 2:51 ` N1nEmAn at proton dot me
@ 2024-04-11 10:53 ` vries at gcc dot gnu.org
2024-04-11 11:33 ` [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted vries at gcc dot gnu.org
` (11 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: vries at gcc dot gnu.org @ 2024-04-11 10:53 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
Looks like a python-specific dup of PR17611.
https://sourceware.org/pipermail/gdb-patches/2024-April/208019.html
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (6 preceding siblings ...)
2024-04-11 10:53 ` vries at gcc dot gnu.org
@ 2024-04-11 11:33 ` vries at gcc dot gnu.org
2024-04-11 12:04 ` N1nEmAn at proton dot me
` (10 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: vries at gcc dot gnu.org @ 2024-04-11 11:33 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|just run gdb and source the |[gdb/python]
|poc can make the memory |inferior.read_memory:
|corrupt/exhausted |internal-error: virtual
| |memory exhausted
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
> just run gdb and source the poc can make the memory corrupt/exhausted
I'm not sure where you see memory corruption.
I'm updating $subject to make the failure mode more clear.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (7 preceding siblings ...)
2024-04-11 11:33 ` [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted vries at gcc dot gnu.org
@ 2024-04-11 12:04 ` N1nEmAn at proton dot me
2024-04-11 12:05 ` vries at gcc dot gnu.org
` (9 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: N1nEmAn at proton dot me @ 2024-04-11 12:04 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
--- Comment #7 from N1nEmAn <N1nEmAn at proton dot me> ---
(In reply to Tom de Vries from comment #6)
> > just run gdb and source the poc can make the memory corrupt/exhausted
>
> I'm not sure where you see memory corruption.
>
> I'm updating $subject to make the failure mode more clear.
you are right. sorry for my unclear descreption.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (8 preceding siblings ...)
2024-04-11 12:04 ` N1nEmAn at proton dot me
@ 2024-04-11 12:05 ` vries at gcc dot gnu.org
2024-04-11 12:16 ` N1nEmAn at proton dot me
` (8 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: vries at gcc dot gnu.org @ 2024-04-11 12:05 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to N1nEmAn from comment #7)
> (In reply to Tom de Vries from comment #6)
> > > just run gdb and source the poc can make the memory corrupt/exhausted
> >
> > I'm not sure where you see memory corruption.
> >
> > I'm updating $subject to make the failure mode more clear.
>
> you are right. sorry for my unclear descreption.
No problem, thanks for reporting this PR.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (9 preceding siblings ...)
2024-04-11 12:05 ` vries at gcc dot gnu.org
@ 2024-04-11 12:16 ` N1nEmAn at proton dot me
2024-04-11 12:21 ` vries at gcc dot gnu.org
` (7 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: N1nEmAn at proton dot me @ 2024-04-11 12:16 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
--- Comment #9 from N1nEmAn <N1nEmAn at proton dot me> ---
(In reply to Tom de Vries from comment #8)
> (In reply to N1nEmAn from comment #7)
> > (In reply to Tom de Vries from comment #6)
> > > > just run gdb and source the poc can make the memory corrupt/exhausted
> > >
> > > I'm not sure where you see memory corruption.
> > >
> > > I'm updating $subject to make the failure mode more clear.
> >
> > you are right. sorry for my unclear descreption.
>
> No problem, thanks for reporting this PR.
Thank you for your recognition. We look forward to your team's resolution of
this issue.
Additionally, I have a question. Can we apply for a CVE for this vulnerability
through MITRE? Or is there another process? I didn't see Sourceware on the CNA
list, but I only saw Glibc.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (10 preceding siblings ...)
2024-04-11 12:16 ` N1nEmAn at proton dot me
@ 2024-04-11 12:21 ` vries at gcc dot gnu.org
2024-04-11 12:26 ` N1nEmAn at proton dot me
` (6 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: vries at gcc dot gnu.org @ 2024-04-11 12:21 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
--- Comment #10 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to N1nEmAn from comment #9)
> (In reply to Tom de Vries from comment #8)
> > (In reply to N1nEmAn from comment #7)
> > > (In reply to Tom de Vries from comment #6)
> > > > > just run gdb and source the poc can make the memory corrupt/exhausted
> > > >
> > > > I'm not sure where you see memory corruption.
> > > >
> > > > I'm updating $subject to make the failure mode more clear.
> > >
> > > you are right. sorry for my unclear descreption.
> >
> > No problem, thanks for reporting this PR.
>
> Thank you for your recognition. We look forward to your team's resolution of
> this issue.
> Additionally, I have a question. Can we apply for a CVE for this
> vulnerability through MITRE? Or is there another process? I didn't see
> Sourceware on the CNA list, but I only saw Glibc.
AFAIU, there's no vulnerability here, just a usability issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (11 preceding siblings ...)
2024-04-11 12:21 ` vries at gcc dot gnu.org
@ 2024-04-11 12:26 ` N1nEmAn at proton dot me
2024-04-11 13:38 ` vries at gcc dot gnu.org
` (5 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: N1nEmAn at proton dot me @ 2024-04-11 12:26 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
--- Comment #11 from N1nEmAn <N1nEmAn at proton dot me> ---
(In reply to Tom de Vries from comment #10)
> (In reply to N1nEmAn from comment #9)
> > (In reply to Tom de Vries from comment #8)
> > > (In reply to N1nEmAn from comment #7)
> > > > (In reply to Tom de Vries from comment #6)
> > > > > > just run gdb and source the poc can make the memory corrupt/exhausted
> > > > >
> > > > > I'm not sure where you see memory corruption.
> > > > >
> > > > > I'm updating $subject to make the failure mode more clear.
> > > >
> > > > you are right. sorry for my unclear descreption.
> > >
> > > No problem, thanks for reporting this PR.
> >
> > Thank you for your recognition. We look forward to your team's resolution of
> > this issue.
> > Additionally, I have a question. Can we apply for a CVE for this
> > vulnerability through MITRE? Or is there another process? I didn't see
> > Sourceware on the CNA list, but I only saw Glibc.
>
> AFAIU, there's no vulnerability here, just a usability issue.
However, I believe that if it is present in pwndbg or any other code that could
exist in gdbinit, it could potentially lead to a local denial-of-service
attack.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (12 preceding siblings ...)
2024-04-11 12:26 ` N1nEmAn at proton dot me
@ 2024-04-11 13:38 ` vries at gcc dot gnu.org
2024-04-11 13:58 ` ssbssa at sourceware dot org
` (4 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: vries at gcc dot gnu.org @ 2024-04-11 13:38 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
--- Comment #12 from Tom de Vries <vries at gcc dot gnu.org> ---
*** Bug 31630 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (13 preceding siblings ...)
2024-04-11 13:38 ` vries at gcc dot gnu.org
@ 2024-04-11 13:58 ` ssbssa at sourceware dot org
2024-04-11 16:00 ` tromey at sourceware dot org
` (3 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: ssbssa at sourceware dot org @ 2024-04-11 13:58 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
Hannes Domani <ssbssa at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ssbssa at sourceware dot org
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (14 preceding siblings ...)
2024-04-11 13:58 ` ssbssa at sourceware dot org
@ 2024-04-11 16:00 ` tromey at sourceware dot org
2024-04-12 2:02 ` N1nEmAn at proton dot me
` (2 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: tromey at sourceware dot org @ 2024-04-11 16:00 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #13 from Tom Tromey <tromey at sourceware dot org> ---
For the record, I think this is not a vulnerability
according to the soon-to-be-landed security policy.
See https://sourceware.org/pipermail/gdb-patches/2024-April/207917.html
So, don't file a CVE.
To my mind it's not even really a gdb bug, more like
"don't do that".
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (15 preceding siblings ...)
2024-04-11 16:00 ` tromey at sourceware dot org
@ 2024-04-12 2:02 ` N1nEmAn at proton dot me
2024-04-16 13:53 ` cvs-commit at gcc dot gnu.org
2024-04-16 13:56 ` vries at gcc dot gnu.org
18 siblings, 0 replies; 20+ messages in thread
From: N1nEmAn at proton dot me @ 2024-04-12 2:02 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
--- Comment #14 from N1nEmAn <N1nEmAn at proton dot me> ---
(In reply to Tom Tromey from comment #13)
> For the record, I think this is not a vulnerability
> according to the soon-to-be-landed security policy.
>
> See https://sourceware.org/pipermail/gdb-patches/2024-April/207917.html
>
> So, don't file a CVE.
>
> To my mind it's not even really a gdb bug, more like
> "don't do that".
ok fine. i see. thanks
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (16 preceding siblings ...)
2024-04-12 2:02 ` N1nEmAn at proton dot me
@ 2024-04-16 13:53 ` cvs-commit at gcc dot gnu.org
2024-04-16 13:56 ` vries at gcc dot gnu.org
18 siblings, 0 replies; 20+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2024-04-16 13:53 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
--- Comment #15 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=06e967dbc9b75a4a3c1b15b54360cf1abbf9c2bd
commit 06e967dbc9b75a4a3c1b15b54360cf1abbf9c2bd
Author: Tom de Vries <tdevries@suse.de>
Date: Tue Apr 16 15:53:47 2024 +0200
[gdb/python] Throw MemoryError in inferior.read_memory if malloc fails
PR python/31631 reports a gdb internal error when doing:
...
(gdb) python gdb.selected_inferior().read_memory (0, 0xffffffffffffffff)
utils.c:709: internal-error: virtual memory exhausted.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
...
Fix this by throwing a python MemoryError, such that we have instead:
...
(gdb) python gdb.selected_inferior().read_memory (0, 0xffffffffffffffff)
Python Exception <class 'MemoryError'>:
Error occurred in Python.
(gdb)
...
Likewise for DAP.
Tested on x86_64-linux.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31631
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
` (17 preceding siblings ...)
2024-04-16 13:53 ` cvs-commit at gcc dot gnu.org
@ 2024-04-16 13:56 ` vries at gcc dot gnu.org
18 siblings, 0 replies; 20+ messages in thread
From: vries at gcc dot gnu.org @ 2024-04-16 13:56 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=31631
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |15.1
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #16 from Tom de Vries <vries at gcc dot gnu.org> ---
Fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2024-04-16 13:56 UTC | newest]
Thread overview: 20+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-04-10 18:33 [Bug gdb/31631] New: just run gdb and source the poc can make the memory corrupt/exhausted N1nEmAn at proton dot me
2024-04-10 18:35 ` [Bug gdb/31631] " N1nEmAn at proton dot me
2024-04-10 20:04 ` vries at gcc dot gnu.org
2024-04-10 20:04 ` [Bug python/31631] " vries at gcc dot gnu.org
2024-04-11 0:05 ` N1nEmAn at proton dot me
2024-04-11 1:48 ` N1nEmAn at proton dot me
2024-04-11 2:51 ` N1nEmAn at proton dot me
2024-04-11 10:53 ` vries at gcc dot gnu.org
2024-04-11 11:33 ` [Bug python/31631] [gdb/python] inferior.read_memory: internal-error: virtual memory exhausted vries at gcc dot gnu.org
2024-04-11 12:04 ` N1nEmAn at proton dot me
2024-04-11 12:05 ` vries at gcc dot gnu.org
2024-04-11 12:16 ` N1nEmAn at proton dot me
2024-04-11 12:21 ` vries at gcc dot gnu.org
2024-04-11 12:26 ` N1nEmAn at proton dot me
2024-04-11 13:38 ` vries at gcc dot gnu.org
2024-04-11 13:58 ` ssbssa at sourceware dot org
2024-04-11 16:00 ` tromey at sourceware dot org
2024-04-12 2:02 ` N1nEmAn at proton dot me
2024-04-16 13:53 ` cvs-commit at gcc dot gnu.org
2024-04-16 13:56 ` vries at gcc dot gnu.org
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).