Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <baurzhan.ismagulov@sbs.com.tr>
To: gdb-patches@sources.redhat.com
Subject: Re: testcase for "absolute source" patch
Date: Wed, 18 Aug 2004 15:50:00 -0000	[thread overview]
Message-ID: <20040818155324.GC1411@ata.cs.hun.edu.tr> (raw)
In-Reply-To: <4123763C.nailM3P11DT7E@mindspring.com>

Hello Michael,

On Wed, Aug 18, 2004 at 11:31:08AM -0400, Michael Chastain wrote:
> So it's okay to leave your "main" with no return type.
> But take out the "-w" from gdb_compile.

I've already specified the return type and removed the flag. I just
wanted to know what I'm doing.


> You would need a hook inside call_remote to send several commands to
> the same shell. Ick!

What about just having pre_cmd and post_cmd in call_remote? Can the same
technique be applied to whatever gets called from gdb_test?


> Alternatively, you would need to forsake gdb_compile and do everything
> at the "remote_exec host cd ... && gcc ... && cd ...", basically
> duplicating the machinery inside default_target_compile to process
> the options (but you know what your own options are) and to find the
> name of the c compiler.

This would work for the compilation, but I'm not sure about gdb_test. Is
there an introduction about the build and host interaction during
gdb_start, gdb_test and gdb_exit?


With kind regards,
Baurjan.


  parent reply	other threads:[~2004-08-18 15:50 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16 14:41 Baurzhan Ismagulov
2004-08-16 15:56 ` Michael Chastain
2004-08-16 18:21   ` Baurjan Ismagulov
2004-08-16 19:15 ` Michael Chastain
2004-08-16 20:38   ` Andreas Schwab
2004-08-18 13:03   ` Baurzhan Ismagulov
2004-08-18 15:31     ` Michael Chastain
2004-08-18 15:50       ` Daniel Jacobowitz
2004-08-18 15:56         ` Baurjan Ismagulov
2004-08-18 16:04           ` Andreas Schwab
2004-08-18 15:50       ` Baurzhan Ismagulov [this message]
2004-08-18 17:10         ` Michael Chastain
2004-08-18 19:00         ` Michael Chastain
2004-08-18 22:03           ` Baurjan Ismagulov
2004-08-18 22:46             ` Michael Chastain
2004-08-18 23:33             ` Michael Chastain
2004-08-19  4:03               ` Eli Zaretskii
2004-08-19  8:34                 ` Michael Chastain
2004-08-19  8:56               ` Michael Chastain
2004-08-19  9:37                 ` Baurjan Ismagulov
2004-08-19  9:34               ` Baurjan Ismagulov
2004-08-19  9:55                 ` Michael Chastain
2004-08-19 10:10                   ` Baurjan Ismagulov
2004-08-19 10:20                     ` Michael Chastain
2004-08-26 20:36                   ` Baurjan Ismagulov
2004-08-26 20:52                     ` Michael Chastain
2004-08-26 20:32               ` Baurjan Ismagulov
2004-08-27 14:16                 ` Michael Chastain
2004-08-27 16:45                   ` Baurjan Ismagulov
2004-08-29 11:56                     ` Michael Chastain
2004-08-31 15:01                     ` Michael Chastain
2004-09-25 21:12                       ` Baurjan Ismagulov

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=20040818155324.GC1411@ata.cs.hun.edu.tr \
    --to=baurzhan.ismagulov@sbs.com.tr \
    --cc=gdb-patches@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