Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #70212 > unrolled thread

gdb python core dump file : not in executable format: File format not

Back to article view | Back to comp.lang.python

Contents

  gdb python core dump file : not in executable format: File format not Wesley <nispray@gmail.com> - 2014-04-14 01:19 -0700
    Re: gdb python core dump file : not in executable format: File format not "david.garvey@gmail.com" <david.garvey@gmail.com> - 2014-04-14 12:37 -0700
      Re: gdb python core dump file : not in executable format: File format not Wesley <nispray@gmail.com> - 2014-04-15 02:39 -0700

#70212 — gdb python core dump file : not in executable format: File format not

Hi guys,
   Today I am debugging an issue related to memory leak.
I use gdb 7.7 and python 2.7.6 to generate one core dump file from production env.

And then, just use gdb to debug the coredump upon the same machine.
Got error that seems not support debug core file using pyton?

Here is snippet:
[root@localhost server]# gdb --core  memleak.core 
GNU gdb (GDB) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
[New LWP 25738]
[New LWP 25739]
[New LWP 25740]
[New LWP 25745]
[New LWP 25746]
[New LWP 25747]
[New LWP 25635]
Core was generated by `python'.
#0  0x00000030016e15e3 in ?? ()
(gdb) file /root/server/deviceserver.py 
"/root/server/deviceserver.py": not in executable format: File format not recognized
(gdb) file /root/server/deviceserver
/root/server/deviceserver: No such file or directory.
(gdb) file /root/server/deviceserver.py 
"/root/server/deviceserver.py": not in executable format: File format not recognized
(gdb) 

[toc] | [next] | [standalone]

#70231

[Multipart message — attachments visible in raw view] — view raw

Does this help?

http://plasmodic.github.io/ecto/ecto/usage/external/debugging.html


http://gnuradio.org/redmine/projects/gnuradio/wiki/TutorialsDebugging


http://downloads.conceptive.be/downloads/camelot/doc/sphinx/build/advanced/debug.html

http://forums.gentoo.org/viewtopic-p-7123814.html


On Mon, Apr 14, 2014 at 1:19 AM, Wesley <nispray@gmail.com> wrote:

> Hi guys,
>    Today I am debugging an issue related to memory leak.
> I use gdb 7.7 and python 2.7.6 to generate one core dump file from
> production env.
>
> And then, just use gdb to debug the coredump upon the same machine.
> Got error that seems not support debug core file using pyton?
>
> Here is snippet:
> [root@localhost server]# gdb --core  memleak.core
> GNU gdb (GDB) 7.7
> Copyright (C) 2014 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-unknown-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
> For help, type "help".
> Type "apropos word" to search for commands related to "word".
> [New LWP 25738]
> [New LWP 25739]
> [New LWP 25740]
> [New LWP 25745]
> [New LWP 25746]
> [New LWP 25747]
> [New LWP 25635]
> Core was generated by `python'.
> #0  0x00000030016e15e3 in ?? ()
> (gdb) file /root/server/deviceserver.py
> "/root/server/deviceserver.py": not in executable format: File format not
> recognized
> (gdb) file /root/server/deviceserver
> /root/server/deviceserver: No such file or directory.
> (gdb) file /root/server/deviceserver.py
> "/root/server/deviceserver.py": not in executable format: File format not
> recognized
> (gdb)
> --
> https://mail.python.org/mailman/listinfo/python-list
>



-- 
David Garvey

[toc] | [prev] | [next] | [standalone]

#70266

在 2014年4月15日星期二UTC+8上午3时37分58秒，david....@gmail.com写道：
> Does this help?
> 
> 
> http://plasmodic.github.io/ecto/ecto/usage/external/debugging.html
> 
> 
> 
> 
> 
> 
> http://gnuradio.org/redmine/projects/gnuradio/wiki/TutorialsDebugging
> 
> 
> 
> 
> 
> http://downloads.conceptive.be/downloads/camelot/doc/sphinx/build/advanced/debug.html
> 
> 
> 
> 
> http://forums.gentoo.org/viewtopic-p-7123814.html
> 
> 
> 
> 
> On Mon, Apr 14, 2014 at 1:19 AM, Wesley <nis...@gmail.com> wrote:
> 
> Hi guys,
> 
>    Today I am debugging an issue related to memory leak.
> 
> I use gdb 7.7 and python 2.7.6 to generate one core dump file from production env.
> 
> 
> 
> And then, just use gdb to debug the coredump upon the same machine.
> 
> Got error that seems not support debug core file using pyton?
> 
> 
> 
> Here is snippet:
> 
> [root@localhost server]# gdb --core  memleak.core
> 
> GNU gdb (GDB) 7.7
> 
> Copyright (C) 2014 Free Software Foundation, Inc.
> 
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> 
> This is free software: you are free to change and redistribute it.
> 
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> 
> and "show warranty" for details.
> 
> This GDB was configured as "x86_64-unknown-linux-gnu".
> 
> Type "show configuration" for configuration details.
> 
> For bug reporting instructions, please see:
> 
> <http://www.gnu.org/software/gdb/bugs/>.
> 
> Find the GDB manual and other documentation resources online at:
> 
> <http://www.gnu.org/software/gdb/documentation/>.
> 
> For help, type "help".
> 
> Type "apropos word" to search for commands related to "word".
> 
> [New LWP 25738]
> 
> [New LWP 25739]
> 
> [New LWP 25740]
> 
> [New LWP 25745]
> 
> [New LWP 25746]
> 
> [New LWP 25747]
> 
> [New LWP 25635]
> 
> Core was generated by `python'.
> 
> #0  0x00000030016e15e3 in ?? ()
> 
> (gdb) file /root/server/deviceserver.py
> 
> "/root/server/deviceserver.py": not in executable format: File format not recognized
> 
> (gdb) file /root/server/deviceserver
> 
> /root/server/deviceserver: No such file or directory.
> 
> (gdb) file /root/server/deviceserver.py
> 
> "/root/server/deviceserver.py": not in executable format: File format not recognized
> 
> (gdb)
> 
> --
> 
> https://mail.python.org/mailman/listinfo/python-list
> 
> 
> 
> 
> 
> -- 
> David Garvey

Yeah， I use gdb --args /usr/local/bin/python ../xxx.py --core xxx.core
Then, 'run' to start script.
However, the core dump file is actually from a memory leak process,which use 1.2 G momory, but now, through info proc, I got proc id, and then, shell pmap proc_id, only 650M, so, seems this is new started proc, not reload env from the core file.

Anything wrong?

Thanks.
Wesley

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web