Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: nickrob@snap.net.nz,  leisner@rochester.rr.com,  gdb@sourceware.org
Subject: Re: breaking on open(2) on linux
Date: Mon, 21 Apr 2008 12:57:00 -0000	[thread overview]
Message-ID: <200804201410.45207.vladimir@codesourcery.com> (raw)
In-Reply-To: <ud4ok3nbv.fsf@gnu.org>

On Sunday 20 April 2008 13:08:52 Eli Zaretskii wrote:
> > From: Vladimir Prus <vladimir@codesourcery.com>
> > Date: Wed, 16 Apr 2008 12:09:30 +0400
> > Cc: nickrob@snap.net.nz,  leisner@rochester.rr.com,  gdb@sourceware.org
> > 
> > On Wednesday 16 April 2008 00:34:30 Eli Zaretskii wrote:
> > > > From: Vladimir Prus <vladimir@codesourcery.com>
> > > > Date: Tue, 15 Apr 2008 12:11:33 +0400
> > > > 
> > > > The multiple location support only works if there line number information
> > > > for all locations.
> > > 
> > > This is important enough to mention in the manual.  Is it there? if it
> > > is, I cannot find it.
> > 
> > It's not there.
> 
> It is now (committed):
> 
> 2008-04-20  Eli Zaretskii  <eliz@gnu.org>
> 
> 	* gdb.texinfo (Set Breaks): Mention that multiple location
> 	breakpoints need line number info.  Add index entries.

Thanks!

- Volodya


  reply	other threads:[~2008-04-20 10:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 23:12 Marty Leisner
2008-04-13  4:18 ` Kip Macy
2008-04-13  6:13 ` Nick Roberts
2008-04-13  6:41   ` Daniel Jacobowitz
2008-04-13 21:38     ` Marty Leisner
2008-04-13 21:41     ` Nick Roberts
2008-04-13 22:05       ` Daniel Jacobowitz
2008-04-15 10:27         ` Vladimir Prus
2008-04-16  0:47           ` Eli Zaretskii
2008-04-16 15:29             ` Vladimir Prus
2008-04-20 14:32               ` Eli Zaretskii
2008-04-21 12:57                 ` Vladimir Prus [this message]
2008-04-13  8:56   ` Marty Leisner

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=200804201410.45207.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=leisner@rochester.rr.com \
    --cc=nickrob@snap.net.nz \
    /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