Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Matt Rice <ratmice@gmail.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Eliminate tui_command_loop
Date: Sat, 10 Sep 2011 16:52:00 -0000	[thread overview]
Message-ID: <CACTLOFroAx9hh0Qk9bh6OTn7fSXaXMwLF=yUb3-NR34NMpOk4w@mail.gmail.com> (raw)
In-Reply-To: <CACTLOFoWEp9RAjA_mv=iXWAtqw_cert7iQ3Dp=ubQ5_+N434Ow@mail.gmail.com>

On Sat, Sep 10, 2011 at 5:46 AM, Matt Rice <ratmice@gmail.com> wrote:

> Sorry to report that there is an issue here,

forgot the reproducer,

./gdb -quiet -ex 'interpreter-exec mi2 "-break-insert main"' -ex start
~/tests/test

e.g.

$ ./gdb/gdb -quiet -ex 'interpreter-exec mi2 "-break-insert main"' -ex
start ~/tests/test
Reading symbols from /home/ratmice/tests/test...done.
^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x0000000000400598",func="main",file="/home/ratmice/tests/test.c",fullname="/home/ratmice/tests/test.c",line="36",times="0",original-location="main"}
(gdb)
Temporary breakpoint 2 at 0x400598: file /home/ratmice/tests/test.c, line 36.
Starting program: /home/ratmice/tests/test

Breakpoint 1, main (argc=1, argv=0x7fffffffe178) at
/home/ratmice/tests/test.c:36
Segmentation fault


  reply	other threads:[~2011-09-10 12:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04 20:11 Pedro Alves
2011-08-04 20:18 ` Tom Tromey
2011-08-05 13:02   ` Pedro Alves
2011-08-05 15:11     ` Tom Tromey
2011-08-04 20:39 ` Thiago Jung Bauermann
2011-08-05  3:49   ` Sergio Durigan Junior
2011-08-05 12:37   ` Pedro Alves
2011-09-10 12:51 ` Matt Rice
2011-09-10 16:52   ` Matt Rice [this message]
2011-09-10 18:47   ` Pedro Alves
2011-09-11  0:46     ` Matt Rice
2011-09-11 14:41       ` Matt Rice
2011-09-13  8:29         ` PR gdb/13175 (Re: Eliminate tui_command_loop) Pedro Alves

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='CACTLOFroAx9hh0Qk9bh6OTn7fSXaXMwLF=yUb3-NR34NMpOk4w@mail.gmail.com' \
    --to=ratmice@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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