09-24-2010
Thank you Jim for replying.
I am running the gdb debugger as u said, but the gdb says the following:
gdb>
Starting program:
No executable file specified.
(I make a Makefile in which it is getting compiled n then it make a target file which gets copied to the robot. I had to do so....coz it had some libraries which needed to be compiled for the robots which were not supported by gnu)
So now after that it sees the file, but it doesn't see the executable file.
So am not sure if this debugger would even work in this case or not.
10 More Discussions You Might Find Interesting
1. Programming
Which is better??
I have always been a gdb fan.. But ppl say dbx is beter better for debugging the core.. Do all GDB lovers agree to it???
:cool: (1 Reply)
Discussion started by: jyotipg
1 Replies
2. Programming
I'm having problem understanding the how to use gdb command to debug my program. Can anyone give me some suggestion how to start, and examples. I read the manual in unix...I'm still confuse. (6 Replies)
Discussion started by: Confuse
6 Replies
3. Shell Programming and Scripting
hello all
im trying to use in sun Solaris the information received from the top command
now i several machines that dont have install the top program so when im running the script im geting error
saying after im running this code :
set MemoryInfo = `top | grep Memory`
if (... (2 Replies)
Discussion started by: umen
2 Replies
4. Solaris
I want to install gdb on SunOS 5.6 machine. Where can i download from ? (1 Reply)
Discussion started by: shafi2all
1 Replies
5. UNIX for Advanced & Expert Users
Hi,
This is a simple question on GDB. Given a core file, how can you check which process has dumped the core?
Regards
- Krishna (1 Reply)
Discussion started by: krishnamurthig
1 Replies
6. UNIX for Advanced & Expert Users
Hi All,
I wanted to know if there is a core file generated and I am not sure for which Binary it is generated .
Can I use gdb to debug the core file ?
Thanks. (1 Reply)
Discussion started by: shubhranshu
1 Replies
7. UNIX for Advanced & Expert Users
Hi All,
I am trying to execute a binary and it is giving Segmentation Fault.
Can I use gdb to debug this error?
Secondly there is no core file generated , so when I an trying to run gdb with the binary only I am not able to set any breakpoints.
When I am running the gdb and the I am... (1 Reply)
Discussion started by: shubhranshu
1 Replies
8. UNIX for Advanced & Expert Users
Hi all
What 's the relationship between gdb and ptrace, if the kernel does
not support ptrace, can gdb work ?
Is there some one can explain this for me (3 Replies)
Discussion started by: yanglei_fage
3 Replies
9. Programming
i have created some break points in gdb.
let's say....
b sqlcxt
how can i know the breakpoint name of sqlcxt ??? (1 Reply)
Discussion started by: lipun4u
1 Replies
10. Programming
Hi, I got:
host machine: RedHat (RHEL6)
virtual machine: RedHat (RHEL6)
I run (on host machine):
qemu-system-x86_64 ...... -S -s
after that i run (on host machine):
gdb
target remote localhost:1234
set architecture i386:x86-64
and then i can use (on host machine) 'ctrl + c' to... (2 Replies)
Discussion started by: Chrisdot
2 Replies
LEARN ABOUT CENTOS
perl::critic::policy::objects::prohibitindirectsyntax
Perl::Critic::Policy::Objects::ProhibitIndirectSyntax(3)User Contributed Perl DocumentatioPerl::Critic::Policy::Objects::ProhibitIndirectSyntax(3)
NAME
Perl::Critic::Policy::Objects::ProhibitIndirectSyntax - Prohibit indirect object call syntax.
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
Indirect object syntax is commonly used in other object-oriented languages for instantiating objects. Perl allows this, but to say that it
supports it may be going too far. Instead of writing
my $foo = new Foo;
it is preferable to write
my $foo = Foo->new;
The problem is that Perl needs to make a number of assumptions at compile time to disambiguate the first form, so it tends to be fragile
and to produce hard-to-track-down bugs.
CONFIGURATION
Indirect object syntax is also hard for Perl::Critic to disambiguate, so this policy only checks certain subroutine calls. The names of the
subroutines can be configured using the "forbid" configuration option:
[Objects::ProhibitIndirectSyntax]
forbid = create destroy
The "new" subroutine is configured by default; any additional "forbid" values are in addition to "new".
CAVEATS
The general situation can not be handled via static analysis.
SEE ALSO
Perl::Critic::Policy::Dynamic::NoIndirect and indirect both do a better job with this, but they require that you compile/execute your code.
AUTHOR
Thomas R. Wyant, III wyant at cpan dot org
COPYRIGHT
Copyright (c) 2009-2011 Tom Wyant.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license
can be found in the LICENSE file included with this module.
perl v5.16.3 2014-06-09 Perl::Critic::Policy::Objects::ProhibitIndirectSyntax(3)