From: "Bobo" <spiridenok@tut.by>
To: gdb@sourceware.org
Subject: Re: Breakpoint in C++ class constructor is never reached
Date: Fri, 26 Oct 2007 14:26:00 -0000 [thread overview]
Message-ID: <web-419223172@speedy.tutby.com> (raw)
In-Reply-To: <20071026122115.GA28419@caradoc.them.org>
Unfortunately i can't do anything with one of the latest snapshots.
I've donwloaded gdb-weekly-6.7.50_20071023.
config goes ok (./configure --enable-gcc --prefix=/scratch/debugger).
make gives the following error:
make: Fatal error in reader: Makefile, line 63: Unexpected end of line seen
Current working directory
/usr/local/gdb-6.7.5/gdb-6.7.50_20071023/libdecnumber
*** Error code 1
make: Fatal error: Command failed for target `all-libdecnumber'
Current working directory /usr/local/gdb-6.7.5/gdb-6.7.50_20071023
*** Error code 1
make: Fatal error: Command failed for target `all'
Is it a known issue? Should somebody submit a bug report for that?
i can build the same version of gdb with gmake (i know this is not the
idea... i just tried to see if it works and it does!). However when i run
the newly built latest version of gdb with my C++ application i got "Symbol
format `elf32-sparc' unknown.". It is solved in 6.7.1 but probably is not
synchronized yet with the latest...
Fri, 26 Oct 2007 08:21:15 -0400, Daniel Jacobowitz <drow@false.org>:
> On Fri, Oct 26, 2007 at 03:18:43PM +0300, Bobo wrote:
>> Sorry i'm not really familiar with GDB release scheme... What is HEAD and
>>where
>> can i find it?
>
> Try snapshots/current on the FTP site, or any link mentioning current
> on the web site.
>
>> One more question: are there any plans to solved this issue in the 6.7
>>release?
>
> No; 6.7 is finished.
>
> --
> Daniel Jacobowitz
> CodeSourcery
---------
Ñà ìûé ñîäåðæà òåëüГûé ïîðòà ë Г® òóðèçìå ГЁ îòäûõå Гў Áåëà ðóñè http://belarustourism.by/
Ãîðîäà Áåëà ðóñè http://belarustourism.by/cities/
Ðà çâëå÷åГГЁГї, à ðõèòåêòóðà , ãîñòèГèöû, áà çû îòäûõà , Гà öèîГà ëüГûå ïà ðêè.
next prev parent reply other threads:[~2007-10-26 14:26 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 [this message]
[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
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-419223172@speedy.tutby.com \
--to=spiridenok@tut.by \
--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).