public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre Petit-Bianco <apbianco@cygnus.com>
To: <rhug-rhats@sources.redhat.com>
Subject: Re: Jython dependencies...
Date: Sat, 20 Oct 2001 21:57:00 -0000	[thread overview]
Message-ID: <15314.21942.373185.694667@fencer.cygnus.com> (raw)
In-Reply-To: <87r8ryduz2.fsf@creche.redhat.com>

Tom Tromey writes:

> This must be specific to the particular program.  With yesterday's
> 3.1 tree, a static hello-world type program works fine.  (I was
> surprised by that.)

Well, I linked statically so I could debug because I never managed to
put my hands on a gdb to would let me debug dynamically linked Java
apps.

Knowing that the GC had a problem with -O2, I rebuilt it appropriately
and started to debug to eventually get the same error the trace
shows. Now the interesting thing is that before rebuilding the GC,
jython would simply say something like `Aborted' but now the
statically or dynamically linked version are printing the trace.

I'm just going to try to rebuild the toolchain without any
optimization, and we'll see. I tried to back Bryce's static ctor
patch, but just going by the message he posted, I get sources that
aren't building -- note that the upgrade after which jython would
crash included that mod (and many others, of course.)

./A

      reply	other threads:[~2001-10-20 21:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-17 17:39 Alexandre Petit-Bianco
2001-10-17 18:30 ` Anthony Green
2001-10-17 18:42   ` Alexandre Petit-Bianco
2001-10-17 18:53 ` Tom Tromey
2001-10-17 19:03   ` Alexandre Petit-Bianco
2001-10-17 21:03 ` Anthony Green
2001-10-17 22:04   ` Alexandre Petit-Bianco
2001-10-19 16:30   ` Alexandre Petit-Bianco
2001-10-20 11:14     ` Tom Tromey
2001-10-20 21:57       ` Alexandre Petit-Bianco [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=15314.21942.373185.694667@fencer.cygnus.com \
    --to=apbianco@cygnus.com \
    --cc=rhug-rhats@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).