Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Christian Thalinger <Christian.Thalinger@Sun.COM>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Tom Tromey <tromey@redhat.com>,
	Tristan Gingold <gingold@adacore.com>,
	        Joel Brobecker <brobecker@adacore.com>,
	        Thiago Jung Bauermann <thiago.bauermann@gmail.com>,
	gdb@sourceware.org
Subject: Re: status of Darwin support
Date: Tue, 11 Aug 2009 16:43:00 -0000	[thread overview]
Message-ID: <4A819F90.40006@Sun.COM> (raw)
In-Reply-To: <8ac60eac0908110933s6caf5abdsa1320f626dea860b@mail.gmail.com>

Paul Pluzhnikov wrote:
>> (gdb) r
>> Starting program:
>> /Users/twisti/bsd-port/hotspot/build/bsd/bsd_i486_compiler2/jvmg/gamma
> 
> I assume these are from debug prints of (section addr? or endaddr?) you've
> added? They look like possibly non-relocated section addresses.

Yes, the same values as the assert compares.

> Could you run gdb under /usr/bin/gdb, like this:
> 
> /usr/bin/gdb --args ./gdb -nx
> /Users/twisti/bsd-port/hotspot/build/bsd/bsd_i486_compiler2/jvmg/gamma
> (top-gdb) break error
> (top-gdb) run
> (gdb) run

I tried that before, but then I get the:

Unable to find Mach task port for process-id 90603: (os/kern) failure (0x5).
 (please check gdb is setgid procmod)

again.  I just tried to run it as root, then it runs but the break does
not work.  I'm confused...

-- Christian


  reply	other threads:[~2009-08-11 16:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16 20:29 Christian Thalinger
2009-08-04 16:52 ` Tom Tromey
2009-08-04 21:03   ` Thiago Jung Bauermann
2009-08-05  4:45     ` Joel Brobecker
2009-08-06 11:14       ` Christian Thalinger
2009-08-06 11:17         ` Jonas Maebe
2009-08-10  9:41         ` Tristan Gingold
2009-08-10 10:47           ` Christian Thalinger
2009-08-10 18:36             ` Tom Tromey
2009-08-10 20:20               ` Paul Pluzhnikov
2009-08-11  5:06                 ` Paul Pluzhnikov
2009-08-11  6:59                   ` Tristan Gingold
2009-08-11  7:14                     ` Paul Pluzhnikov
2009-08-11  7:43                       ` Tristan Gingold
2009-08-11  8:20                       ` Christian Thalinger
2009-08-11  8:28                 ` Christian Thalinger
2009-08-11 16:33                   ` Paul Pluzhnikov
2009-08-11 16:43                     ` Christian Thalinger [this message]
2009-08-11 16:48                       ` Paul Pluzhnikov
2009-08-11 16:49                       ` Christian Thalinger
2009-08-11 17:12                         ` Paul Pluzhnikov
2009-08-11 17:25                           ` Christian Thalinger
2009-08-11 17:38                             ` Paul Pluzhnikov
2009-08-11 17:54                               ` Christian Thalinger
2009-08-12 16:26                               ` Paul Pluzhnikov
2009-08-12 16:45                                 ` Christian Thalinger
2009-08-26  0:18                   ` [patch] [new testcase] Regression on qsort_cmp [Re: status of Darwin support] Jan Kratochvil
2009-09-08  9:31                     ` Tristan Gingold
2009-09-08 13:04                       ` Jack Howarth
2009-08-06 10:51     ` status of Darwin support Christian Thalinger

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=4A819F90.40006@Sun.COM \
    --to=christian.thalinger@sun.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=gingold@adacore.com \
    --cc=ppluzhnikov@google.com \
    --cc=thiago.bauermann@gmail.com \
    --cc=tromey@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