Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: shaunj@gray-interfaces.com
Cc: gdb@sources.redhat.com, insight@sources.redhat.com
Subject: Re: gdb and jeeni
Date: Thu, 03 Aug 2000 13:51:00 -0000	[thread overview]
Message-ID: <3989DB31.C353C116@cygnus.com> (raw)
In-Reply-To: <00080313412800.00552@ed>

Wrong list.  This should have been posted to insight@sourceware.cygnus.com as it is
a GUI only problem.

Anyway, I can't reproduce this problem here.  Something is really bad with your Tcl
as it is generating a combobox event (which is the only case the change_baud is called).

I don't know what is causing this spurious call, but I can add a guard against this.
Please try the attached patch and let me know if it solved your problem.

Thanks.

Fernando

P.S.: Please drop the gdb list when replying.  Thanks.



Shaun Jackman wrote:
> 
> I'm running Insight 5.0 --target=arm-elf --host=i686-pc-linux-gnu and a jeeni
> (ARM Angel/Ethernet). When I click "Target Settings" I get the error 'No symbol
> "ETH" in current context.'
> The stack trace is:
> No symbol "ETH" in current context.
> 
>     while executing
> "gdb_cmd "set remotebaud $baud""
>     (object "::.targetselection0.targetselection" method "::TargetSelection::change_baud" body line 4)
>     invoked from within
> "::.targetselection0.targetselection change_baud .targetselection0.targetselection.f.lab.lf.childsite.cb ETH"
>     (in namespace inscope "::TargetSelection" script line 1)
>     invoked from within
> "namespace inscope ::TargetSelection {::.targetselection0.targetselection change_baud} .targetselection0.targetselection.f.lab.lf.childsite.cb ETH"
>     ("after" script)errorCode is NONE
> 
> Cheers,
> Shaun



===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/library/targetselection.itb,v
retrieving revision 1.1.1.1
diff -c -p -r1.1.1.1 targetselection.itb
*** targetselection.itb 2000/02/07 00:19:42     1.1.1.1
--- targetselection.itb 2000/08/03 20:49:38
*************** body TargetSelection::change_target {w {
*** 769,775 ****
  # ------------------------------------------------------------------
  body TargetSelection::change_baud {w {baud ""}} {
    if {$baud != ""} {
!     if {[string compare $baud "TCP"] != 0} {
        gdb_cmd "set remotebaud $baud"
        if {[catch {gdb_cmd "show remotebaud"} res]} {
        set newbaud 0
--- 769,776 ----
  # ------------------------------------------------------------------
  body TargetSelection::change_baud {w {baud ""}} {
    if {$baud != ""} {
!     if {([string compare $baud "TCP"] != 0)
!         && ([string compare $baud "ETX"] != 0)} {
        gdb_cmd "set remotebaud $baud"
        if {[catch {gdb_cmd "show remotebaud"} res]} {
        set newbaud 0



-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@cygnus.com
2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
Toronto, Ontario   M4P 2C9              Fax:  416-482-6299
From ngupta@zumanetworks.com Thu Aug 03 15:57:00 2000
From: "niraj gupta" <ngupta@zumanetworks.com>
To: <gdb@sources.redhat.com>
Subject: build isuues with m68k-linux target on x86 host
Date: Thu, 03 Aug 2000 15:57:00 -0000
Message-id: <000f01bffd9d$7f3d9ba0$d301a8c0@internal.nbase.com>
X-SW-Source: 2000-08/msg00030.html
Content-length: 332

i get unresolved on  in_sigtramp()

changing in tm-linux.h

#define IN_SIGTRAMP(pc,name) in_sigtramp (pc)
extern int in_sigtramp (CORE_ADDR pc);

to

extern int delta68_in_sigtramp (CORE_ADDR pc, char *name);
#define IN_SIGTRAMP(pc,name) delta68_in_sigtramp (pc, name)


seems to work, don't know if this is the right change

niraj
From kevinb@cygnus.com Thu Aug 03 16:23:00 2000
From: Kevin Buettner <kevinb@cygnus.com>
To: "niraj gupta" <ngupta@zumanetworks.com>, <gdb@sources.redhat.com>
Subject: Re: build isuues with m68k-linux target on x86 host
Date: Thu, 03 Aug 2000 16:23:00 -0000
Message-id: <1000803232327.ZM3079@ocotillo.lan>
References: <000f01bffd9d$7f3d9ba0$d301a8c0@internal.nbase.com> <ngupta@zumanetworks.com>
X-SW-Source: 2000-08/msg00031.html
Content-length: 1031

On Aug 3,  3:52pm, niraj gupta wrote:

> i get unresolved on  in_sigtramp()
> 
> changing in tm-linux.h
> 
> #define IN_SIGTRAMP(pc,name) in_sigtramp (pc)
> extern int in_sigtramp (CORE_ADDR pc);
> 
> to
> 
> extern int delta68_in_sigtramp (CORE_ADDR pc, char *name);
> #define IN_SIGTRAMP(pc,name) delta68_in_sigtramp (pc, name)
> 
> 
> seems to work, don't know if this is the right change

I doubt it.  My recollection is that the Delta 68 is a very
old m68k machine made by Motorola.  (When I used them, they
ran SVR3.)

It is very unlikely that the mechanism for detecting that you're
in the signal trampoline code is the same for both linux and the old
delta68s.

It looks to me like you need to move in_sigtramp() from m68klinux-nat.c
to m68k-tdep.c.  (Also, you'll want to rename it to something like
m68klinux_in_sigtramp()).

After looking at in_sigtramp() in m68klinux-nat.c, I see absolutely
no reason for it being there.  It looks to me like it should build
just fine if moved (and renamed) to the tdep.c file.

Kevin
From gerwynd@tommoll.freeserve.co.uk Thu Aug 03 17:06:00 2000
From: "Gerwyn Davies" <gerwynd@tommoll.freeserve.co.uk>
To: "GDB" <gdb@sourceware.cygnus.com>
Subject: GDB error messages
Date: Thu, 03 Aug 2000 17:06:00 -0000
Message-id: <002301bffda8$4e0d70e0$ec08883e@gtd-s-machine>
X-SW-Source: 2000-08/msg00032.html
Content-length: 243

Hi,

A could anyone tell me what the cause is of the following GDB error
messages:-

"Don't know how to run" in response to a 'run' command.
and
"You can't do that when your target is `exec' " in response to a load
command.

Thanks

Gerwyn




       reply	other threads:[~2000-08-03 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00080313412800.00552@ed>
2000-08-03 13:51 ` Fernando Nasser [this message]
2000-08-08 15:33   ` Fernando Nasser

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=3989DB31.C353C116@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=shaunj@gray-interfaces.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