From: Joel Brobecker <brobecker@gnat.com>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfa] hppa-linux target, 2nd try
Date: Sun, 25 Apr 2004 00:25:00 -0000 [thread overview]
Message-ID: <20040425002520.GP2811@gnat.com> (raw)
In-Reply-To: <20040424192614.GD2923@tausq.org>
> At least 20% of those failures is because malloc() calls to the inferior
> are not working (they cause the inferior to segfault). There are also
> some problems with watchpoints and multithreaded apps. Definitely
> more work to do, but this is much better than before :)
I actually started looking at that about 10 days ago, but it is hard for
me to figure out what is going wrong, because I don't know too well the
machinery for calling functions inside shared libraries. And then I got
pre-empted by something else.
It's something that's on my reasonably-near-future list.
--
Joel
next prev parent reply other threads:[~2004-04-25 0:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-24 19:26 Randolph Chung
2004-04-25 0:25 ` Joel Brobecker [this message]
2004-04-25 0:30 ` Randolph Chung
2004-04-28 15:54 ` Andrew Cagney
2004-04-25 6:07 ` Randolph Chung
2004-04-28 15:58 ` Andrew Cagney
2004-04-28 16:00 ` Randolph Chung
2004-04-28 20:53 ` Andrew Cagney
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=20040425002520.GP2811@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.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