From: "Bobo" <spiridenok@tut.by>
To: Daniel Jacobowitz <drow@false.org>,Thiago Jung Bauermann
<bauerman@br.ibm.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Breakpoint in C++ class constructor is never reached
Date: Thu, 08 Nov 2007 16:29:00 -0000 [thread overview]
Message-ID: <web-428000382@speedy.tutby.com> (raw)
In-Reply-To: <20071108150514.GA30051@caradoc.them.org>
configuring with --disable-tui solves the linking problem. Because i use ddd
as a GUI frontend for gdb i dont really need the tui.
Finally i was able to run gdb and to check if i can set breakpoints in
constructors/destructors of my c++ classes. It works fine! Great work guys!
Thiago, please let me know when your solaris build fix is in the repository.
I'll use then the official snapshot i.s.o. patching the files manually.
Daniel, do i understand correctly that there will be no 6.7.5 release of
gdb? Is it correct that the next official release (with my issues solved) is
planned for Feb 2008?
Thu, 8 Nov 2007 10:05:14 -0500, Daniel Jacobowitz <drow@false.org>:
> On Thu, Nov 08, 2007 at 12:58:41PM -0200, Thiago Jung Bauermann wrote:
>> Hi,
>>
>> The symbols that are missing should come from the curses library. Do you
>> have it installed?
>
> I believe this is a frequent problem caused by having curses in /usr
> and ncurses in /usr/local. If someone's feeling especially motivated
> to make our configure script handle this better... It happens because
> GCC searches /usr/local/include but not /usr/local/lib.
>
> Otherwise, use --disable-tui to configure or LDFLAGS=-L/usr/local/lib.
>
>
> --
> Daniel Jacobowitz
> CodeSourcery
------------------
Ôîðåêñ Êëóáó 10 ëåò! http://www.forexclub.by
next prev parent reply other threads:[~2007-11-08 16:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 11:45 Bobo
2007-10-26 11:54 ` Daniel Jacobowitz
2007-10-26 12:18 ` Bobo
2007-10-26 12:21 ` Daniel Jacobowitz
2007-10-26 14:26 ` Bobo
[not found] ` <web-419222549@speedy.tutby.com>
2007-10-26 14:31 ` Daniel Jacobowitz
2007-10-26 14:51 ` Mark Kettenis
2007-10-26 14:59 ` Daniel Jacobowitz
2007-10-26 15:02 ` Thiago Jung Bauermann
2007-10-27 14:32 ` Thiago Jung Bauermann
2007-10-27 15:57 ` Mark Kettenis
2007-10-30 9:53 ` Bobo
2007-10-30 11:19 ` Daniel Jacobowitz
2007-10-30 13:50 ` Thiago Jung Bauermann
2007-10-30 14:13 ` Thiago Jung Bauermann
2007-10-31 8:10 ` Bobo
2007-10-31 19:06 ` Thiago Jung Bauermann
2007-11-05 9:01 ` Bobo
2007-11-06 20:12 ` Thiago Jung Bauermann
2007-11-07 8:31 ` Bobo
2007-11-07 20:34 ` Thiago Jung Bauermann
2007-11-08 8:27 ` Bobo
2007-11-08 14:58 ` Thiago Jung Bauermann
2007-11-08 15:05 ` Daniel Jacobowitz
2007-11-08 16:29 ` Bobo [this message]
2007-11-08 16:33 ` Daniel Jacobowitz
2007-11-09 7:38 ` Bobo
2007-11-09 14:02 ` Daniel Jacobowitz
2007-11-16 15:26 ` Bobo
2007-11-26 19:11 ` Thiago Jung Bauermann
2007-11-06 15:58 ` Gordon Prieur
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=web-428000382@speedy.tutby.com \
--to=spiridenok@tut.by \
--cc=bauerman@br.ibm.com \
--cc=drow@false.org \
--cc=gdb@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).