From: Andrew Cagney <ac131313@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: HP/UX 10.20 and 11.0 broken in 5.1
Date: Tue, 16 Oct 2001 10:40:00 -0000 [thread overview]
Message-ID: <3BCC70FE.4010205@cygnus.com> (raw)
In-Reply-To: <3BCB9DF9.2070809@cygnus.com>
> I intend cutting my losses on this. (And I bet this isn't going to down well in some quarters).
>
> 11.0 trips up on a problem in ltconfig during configure.
>
> 10.20 doesn't build with HP's `cc -Ae' compiler. It builds with GCC but doesn't work.
Just by way of supporting evidence :-)
The attached patch was a quick attempt at addressing the GCC warnings.
The thing to notice is that fixing the warnings involves cleaning up
core-gdb include files.
enjoy,
Andrew
From kimball@sgrail.com Tue Oct 16 13:11:00 2001
From: Kimball Thurston <kimball@sgrail.com>
To: gdb@sources.redhat.com
Subject: gdb and dlopen
Date: Tue, 16 Oct 2001 13:11:00 -0000
Message-id: <y3radyrjqf8.wl@paladin.sgrail.com>
X-SW-Source: 2001-10/msg00157.html
Content-length: 610
Hey all,
In our application, we've got a plugin architecture that, under
unix, we open using dlopen et al. When trying to debug using gdb, the
process of calling dlopen seems to take an extraordinary amount of
time, as it looks like gdb is using ptrace to copy a bunch of the
debug process's memory at each dlopen into itself. Is there a way to
delay this behavior, or disable it all together, or fix it? I couldn't
determine exactly how gdb uses the memory it copies in. All I know is
it makes using gdb nearly impossible when you have to wait 10 minutes
for the program to start up...
thanks,
Kimball
prev parent reply other threads:[~2001-10-16 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-15 19:40 Andrew Cagney
2001-10-15 20:09 ` gdb
2001-10-15 20:44 ` Andrew Cagney
2001-10-16 10:40 ` Andrew Cagney [this message]
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=3BCC70FE.4010205@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.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