public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "joachim.protze at zih dot tu-dresden.de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/11914] Multiple call to inferior function can leed to segfault
Date: Fri, 11 Feb 2011 12:09:00 -0000	[thread overview]
Message-ID: <bug-11914-4717-WEGAHCsoBX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11914-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=11914

--- Comment #1 from Joachim Protze <joachim.protze at zih dot tu-dresden.de> 2011-02-11 12:09:09 UTC ---
The bug is still reproducible in current weekly snapshot:

$ gdb a.out
GNU gdb (GDB) 7.2.50.20110208
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/jprotze/pptest/a.out...done.
(gdb) source pptest.py
(gdb) b 30
Breakpoint 1 at 0x4004ac: file pptest.c, line 30.
(gdb) r
Starting program: /home/jprotze/pptest/a.out 

Breakpoint 1, main (argc=1, argv=0x7fffffffe198) at pptest2.c:30
30        f=5;
(gdb) python
>for i in range(10000):
>  gdb.execute("info locals", False, True)
>end
Segmentation fault

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


       reply	other threads:[~2011-02-11 12:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11914-4717@http.sourceware.org/bugzilla/>
2011-02-11 12:09 ` joachim.protze at zih dot tu-dresden.de [this message]
2011-06-30 12:01 ` pmuldoon at redhat dot com
2011-07-19 15:27 ` joachim.protze at zih dot tu-dresden.de
2011-07-19 15:56 ` pmuldoon at redhat dot com
2011-07-19 18:39 ` jan.kratochvil at redhat dot com
2012-07-14 20:51 ` jan.kratochvil at redhat dot com
2012-07-16 19:16 ` cvs-commit at gcc dot gnu.org
2012-07-16 19:19 ` jan.kratochvil at redhat dot com
2014-02-16 19:20 ` jackie.rosen at hushmail dot com
2014-05-28 19:47 ` schwab at sourceware dot org
2014-05-28 19:47 ` schwab at sourceware dot org

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=bug-11914-4717-WEGAHCsoBX@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).