Hello Héctor,
On Tue, 28 Nov 2023 13:37:40 +0100
=?UTF-8?B?SMOpY3RvciBPcsOzbiBNYXJ0w61uZXo=?= wrote:
> I wanted to drop a link to addr2line bug[1], could that be related?
>
> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=29785
Thanks for this link.
It looks like it can be related, but
Hello tomazzi,
On Sun, 26 Nov 2023 at 19:45, tomazzi wrote:
> I have found the root cause of this problem:
Thanks very much! This is a very valuable investigation.
I wanted to drop a link to addr2line bug[1], could that be related?
[1] https://sourceware.org/bugzilla/show_bug.cgi?id=29785
> I
Hello,
I have found the root cause of this problem:
It doesn't matter if the gdb is compiled with sbuild, debuild or
dpkg-buildpackage. It's slow, because it reads BFDs from a *hidden*
directory "/usr/lib/debug/.build-id/"
The gdb compiled using "configure" script had different prefix, so its
Hello,
On Tue, 21 Nov 2023 13:53:00 +0100
=?UTF-8?B?SMOpY3RvciBPcsOzbiBNYXJ0w61uZXo=?= wrote:
> Hello,
>
> On Wed, 15 Nov 2023 at 23:09, tomazzi wrote:
>
> > To do this, I need to have a complete build log with all the
> > compiler/linker flags, compiler warnings, etc.
>
> Find logs at https
Hello,
On Wed, 15 Nov 2023 at 23:09, tomazzi wrote:
> To do this, I need to have a complete build log with all the
> compiler/linker flags, compiler warnings, etc.
Find logs at https://buildd.debian.org/status/logs.php?pkg=gdb&arch=amd64
> Unfortunately, the methods described on the official D
Hello Héctor,
Well, I want to fix this bug, because gdb is a very important tool for
me, and compiling gdb from ./configure script is just a hack - not a
real solution (which would eliminate the problem for good).
To do this, I need to have a complete build log with all the
compiler/linker f
Hello Tomazzi,
On Mon, 13 Nov 2023 at 21:51, tomazzi wrote:
>
> Hello,
>
> I've just built gdb "the Debian way", to check what are the differences
> in the build process:
> $> apt source gdb
> $> apt build-dep gdb
> $> debuild -b -uc -us
>
> From debuild output:
>
> gdb-default: configured with:
Hello,
I've just built gdb "the Debian way", to check what are the differences
in the build process:
$> apt source gdb
$> apt build-dep gdb
$> debuild -b -uc -us
From debuild output:
gdb-default: configured with:
...
--without-babeltrace
--with-babeltrace
...
gdb-minimal: configured
Today I've tried to do the same trick on some other machine (using build
flags from previous mail), but the build failed with error message:
"ar: `u' modifier ignored since `D' is the default (see `U')"
while compiling "libgdbsupport.a"
So I've just spent few hours trying to figure out why it wo
Package: gdb
Version: 13.1-3
Severity: important
X-Debbugs-Cc: tomasz.paw...@wp.eu
The gdb compiled for Debian12 is extremely slow - it takes tens of seconds to
minutes
to execute even the simplest commands, like "info args", or "backtrace" - for a
medium size program.
I've modified Codeblocks ID
10 matches
Mail list logo
