From: Daniel Jacobowitz <drow@false.org>
To: Rob Quill <rob.quill@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: TODO List?
Date: Sun, 14 May 2006 05:34:00 -0000 [thread overview]
Message-ID: <20060514041846.GB18922@nevyn.them.org> (raw)
In-Reply-To: <baf6008d0605131011s4ab12683s4c4ce7b6b67f93d8@mail.gmail.com>
On Sat, May 13, 2006 at 06:11:41PM +0100, Rob Quill wrote:
> Is it cool to ask anything GDB related on here? I imagine I'll be
> using the list quite a lot over the coming months as I try to get to
> grips with the code. Do you have any suggestions for how to go about
> this? I have downloaded the GDB Internals document, and will be having
> a look through that. Do you have any other suggestions for how to go
> about getting to grips with the code? Also, is it alright to ask
> questions about the GDB Internals document on here, if there are
> things I don't understand.
Yes, that all sounds fine.
If you've got time to kill and want to poke around the code, feel free
to pick bugs out of the GNATS database :-)
[If you intend for your research work to be usable by and incorporated
into mainline GDB some day, you may want to work on copyright
assignment paperwork. Since this is university research work, the
university would have to submit some paperwork too - this can take ages
to sort out, so if you want it done, it's good to start early :-)]
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-14 4:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 14:54 Rob Quill
2006-05-13 17:14 ` Daniel Jacobowitz
2006-05-13 21:57 ` Rob Quill
2006-05-14 5:34 ` Daniel Jacobowitz [this message]
2006-05-14 15:02 ` Robert Dewar
2006-05-14 15:06 ` Rob Quill
2006-05-14 15:10 ` Daniel Jacobowitz
2006-05-14 19:34 ` Robert Dewar
2006-05-14 21:22 ` Daniel Jacobowitz
2006-05-15 18:41 ` PAUL GILLIAM
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=20060514041846.GB18922@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=rob.quill@gmail.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