public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "'gdb\@sourceware.org'" <gdb@sourceware.org>
Subject: Re: Pending breakpoints on lines that don't exist
Date: Wed, 04 Jan 2012 20:49:00 -0000	[thread overview]
Message-ID: <m38vln6vmp.fsf@fleche.redhat.com> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC578D18D642@EUSAACMS0703.eamcs.ericsson.se>	(Marc Khouzam's message of "Tue, 3 Jan 2012 16:30:21 -0500")

>>>>> "Marc" == Marc Khouzam <marc.khouzam@ericsson.com> writes:

Marc> (gdb) b 2
Marc> No line 2 in the current file.
Marc> Make breakpoint pending on future shared library load? (y or [n]) y
Marc> Breakpoint 1 (2) pending.

This is intended, but I wonder whether it would make sense to have
different behavior in the case where the file is implicit.

That is, "b 2" would just give the old error, but "b currentfile.c:2"
would prompt for a pending breakpoint.

The rationale for this would be that, in the implicit filename case, the
user is presumably asking for exactly the current file.

Tom

  parent reply	other threads:[~2012-01-04 20:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 21:30 Marc Khouzam
2012-01-04  3:52 ` Joel Brobecker
2012-01-04  5:07   ` Eli Zaretskii
2012-01-04  7:17     ` Joel Brobecker
2012-01-04  8:08       ` Eli Zaretskii
2012-01-04  9:13         ` Joel Brobecker
2012-01-06  2:30   ` Marc Khouzam
2012-01-04 20:49 ` Tom Tromey [this message]
2012-01-05 12:56   ` Pedro Alves
2012-01-04 14:28 Richard Guenther
2012-01-04 14:29 ` Richard Guenther
2012-01-04 20:42 ` Tom Tromey

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=m38vln6vmp.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=marc.khouzam@ericsson.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).