From: "Monika Chaddha" <monika@acmet.com>
To: "'Arun Vishwanathan'" <arun.vishwanathan@nevisnetworks.com>,
"'True Sylvia'" <truesylvia@yahoo.co.uk>
Cc: <gdb@sources.redhat.com>
Subject: RE: Strange GDB behavior
Date: Mon, 26 Jul 2004 13:00:00 -0000 [thread overview]
Message-ID: <008a01c47309$08a04e80$5100a8c0@monika> (raw)
In-Reply-To: <36993D449C7FA647BF43568E0793AB3E4E3161@nevis_pune_xchg.pune.nevisnetworks.com>
> Hence I think this statement is incorrect
>> (gdb) p *bnp->as_count
Yes I m agree with u that this is incorrect but in this case also it
should give error like
if as_count=0
"Cannot access memory at address 0x0"
and it should not give like " There is no member named egp_options."
Regards
Monika
>
>It should be
>
>(gdb) p bnp->as_count
>
>
>-----Original Message-----
>From: gdb-owner@sources.redhat.com
[mailto:gdb-owner@sources.redhat.com] On
>Behalf Of Arun Vishwanathan
>Sent: Monday, July 26, 2004 5:18 PM
>To: Monika Chaddha; True Sylvia
>Cc: gdb@sources.redhat.com
>Subject: RE: Strange GDB behavior
>
>>From your following command it is evident that "bnp" is a pointer to a
>structure.
>
>>(gdb) p *bnp
>>$1 = {egp_next = 0x0, egp_sort_next = 0x0, egp_group = 0x82a45ef0,
>> egp_flags = 138412032, egp_hisrcvdcaps = 0, egp_hiscaps = 0,
egp_conf
>= {
>> action = 0 '\000'}, egpc_peer_as = 0, egpc_description = 0x0,
>>as_count
>>= 0,
>> ---Type <return> to continue, or q <return> to quit---q
>>Quit
>
>
> Hence I think this statement is incorrect
>> (gdb) p *bnp->as_count
>
>It should be
>
>(gdb) p bnp->as_count
>
>
>
>Regards,
>Arun
>
>-----Original Message-----
>From: gdb-owner@sources.redhat.com
[mailto:gdb-owner@sources.redhat.com]
>On Behalf Of Monika Chaddha
>Sent: Monday, July 26, 2004 4:51 PM
>To: 'True Sylvia'
>Cc: gdb@sources.redhat.com
>Subject: RE: Strange GDB behavior
>
>Hi Sylvia,
>
>Compile yours source code with option -O0 and than try again.... As
this
>can be a problem due to optimization...
>Are you getting the same problem with the other structures also?
>
>Regards
>Monika
>
>>-----Original Message-----
>>From: True Sylvia [mailto:truesylvia@yahoo.co.uk]
>>Sent: Monday, July 26, 2004 2:24 PM
>>To: gdb@sources.redhat.com
>>Subject: Strange GDB behavior
>>
>>Hi,
>>
>>Am using the following flavor of GDB
>>
>>Current directory is /tftproot/code/
>>GDB is free software and you are welcome to distribute copies of it
>> under certain conditions; type "show copying" to see the conditions.
>>There is absolutely no warranty for GDB; type "show warranty" for
>details.
>>GDB 4.16 (sparc-sun-solaris2.5.1 --target mips64orion-elf),
>>Copyright 1996 Free Software Foundation, Inc...
>>(gdb)
>>
>>I have attached GDB to my executable and the following happens when i
>stop
>>on one of the breakpoints that i have set
>>
>>(gdb) info br
>>Num Type Disp Enb Address What
>>1 breakpoint keep y 0x8087c728 in egp_peer_close at
>egp_init.c:5265
>>(gdb)
>>(gdb) c
>>Continuing.
>>[New thread 22682896]
>>[Switching to thread 22682896]
>>
>>Breakpoint 1, egp_peer_close (bnp=0x82a461c8, event=2) at
>egp_init.c:5265
>>(gdb) p *bnp
>>$1 = {egp_next = 0x0, egp_sort_next = 0x0, egp_group = 0x82a45ef0,
>> egp_flags = 138412032, egp_hisrcvdcaps = 0, egp_hiscaps = 0,
egp_conf
>= {
>> action = 0 '\000'}, egpc_peer_as = 0, egpc_description = 0x0,
>>as_count
>>= 0,
>> ---Type <return> to continue, or q <return> to quit---q
>>Quit
>>(gdb)
>>
>>(gdb) p *bnp->as_count
>>There is no member named as_count.
>>(gdb)
>>(gdb) p *bnp->egp_options
>>There is no member named egp_options.
>>
>>*Why* is this happening? I have members as_count and egp_options in my
>bnp
>>structure. Why isnt GDB showing me thses?
>>
>>Regards,
>>Sylvia T.
>>
>
next prev parent reply other threads:[~2004-07-26 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 11:58 Arun Vishwanathan
2004-07-26 13:00 ` Monika Chaddha [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-26 12:09 Atul Talesara
2004-07-26 11:34 True Sylvia
2004-07-26 11:48 ` Monika Chaddha
2004-07-26 13:15 ` Daniel Jacobowitz
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='008a01c47309$08a04e80$5100a8c0@monika' \
--to=monika@acmet.com \
--cc=arun.vishwanathan@nevisnetworks.com \
--cc=gdb@sources.redhat.com \
--cc=truesylvia@yahoo.co.uk \
/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