> From: Francesco Potorti` <[EMAIL PROTECTED]>
> Date: Tue, 22 Jan 2002 12:27:11 +0100
>
> (gdb) p/x current_buffer->auto_save_file_name
> $59 = 0x1827b31c
> (gdb) xstring
> $60 = (struct Lisp_String *) 0x827b31c
> Segmentation fault (core dumped)
Does GDB's core file say something interesting a
> From: Francesco Potorti` <[EMAIL PROTECTED]>
> Date: Sat, 26 Jan 2002 17:22:23 +0100
>
> As far as I can tell, the backtrace of gdb's core looks like the
> backtrace of a dumped Emacs, but it is different from the real backtrace
> of the Emacs that was being debugged.
Sorry, I don't understand
On Mon, 28 Jan 2002, Francesco Potorti` wrote:
> The most probable cause should be trying to access something out of the
> user space.
As others pointed out, GDB should not crash when it reads the debuggee's
memory, even if the pointer is invalid. The debug interface should
return a failure i
> From: "Nikos Balkanas" <[EMAIL PROTECTED]>
> Date: Mon, 21 Mar 2005 04:42:19 +0200
>
> Problem:
>
> (1) Source lines get messed up
> (2) Just evaluated variables, are "out of context" (may be previous
> problem)
These all happen because of the compiler optimizations (the -O2 switch
to GCC):
>
> From: Casey Callaghan <[EMAIL PROTECTED]>
> Date: Fri, 8 Apr 2005 14:58:28 +0200
>
> (gdb) watch *(Hidden *)0xb190
> Watchpoint 2: *(Bug::Hidden *) 3221221776
Here, GDB sets a software watchpoint on that address (because the
Hidden object is too large to watch it with x86 debug registers).
object to the following patch?
2005-04-27 Eli Zaretskii <[EMAIL PROTECTED]>
* cli/cli-cmds.c (edit_command): Use symtab->fullname if
possible. Use IS_ABSOLUTE_PATH instead of checking for a literal
'/'. Make sure there's a slash between the directory
logic is
> unnecessary; if symtab_to_fullname fails, GDB does not know where the
> file is.
Thanks for the tip. Here's the revised patch:
2005-04-27 Eli Zaretskii <[EMAIL PROTECTED]>
* cli/cli-cmds.c (edit_command): If symtab->fullname is not yet
set, use symta
> Date: Wed, 27 Apr 2005 14:04:10 -0400
> From: Daniel Jacobowitz <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED], bug-gdb@gnu.org, [EMAIL PROTECTED]
>
> It strikes me as odd that you can use "edit" if GDB doesn't know where
> the source file is.
I thought about that, and decided to leave that code a
e shell. (I use "..." for quoting because this is more portable to
various shells, including on Windows.)
Thanks to Daniel and Mark for valuable input.
2005-04-28 Eli Zaretskii <[EMAIL PROTECTED]>
* cli/cli-cmds.c (edit_command): If symtab->fullname is not yet
> Date: Thu, 28 Apr 2005 16:42:01 -0400
> From: Daniel Jacobowitz <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED], bug-gdb@gnu.org, [EMAIL PROTECTED]
>
> The use of "" is not a bulletproof quoting mechanism
Yep, known. But it's IMHO the most portable one can get without going
into the pains of quote
> Date: Thu, 28 Apr 2005 17:18:03 -0400
> From: Daniel Jacobowitz <[EMAIL PROTECTED]>
> Cc: bug-gdb@gnu.org, [EMAIL PROTECTED]
>
> Or using a mechanism to start other processes that takes an argument
> vector :-)
Unfortunately, that's not a magic wand, either. Specifically, in the
case in point,
> Date: Fri, 27 May 2005 22:55:31 +0400
> From: "Ilya N. Golubev" <[EMAIL PROTECTED]>
>
> Version: 6.3
>
> Can not rebuild `gdb.info' even by explicit command. At least one
> required file is neither in distribution nor gets built.
gdb-cfg.texi is a generated file. If you say "make info", it w
> Date: Fri, 27 May 2005 22:48:46 +0400
> From: "Ilya N. Golubev" <[EMAIL PROTECTED]>
>
> Version: 6.3
>
> `make' does not even try to build `gdb.info'.
>
> ../share/gdb-6.3/configure&&make
> rm ../share/gdb-6.3/gdb/doc/gdb.info*
> make
> ls ../share/gdb-6.3/gdb/doc/gdb.info*
>
> ls: ../share/g
> Date: Mon, 30 May 2005 22:08:17 +0400
> From: "Ilya N. Golubev" <[EMAIL PROTECTED]>
> CC: bug-gdb@gnu.org
>
> if `gdb.texinfo' or other `gdb.info' prerequisite was changed, will
> `make install' install updated `gdb.info' version?
Yes, it should.
> The worst is that distribution does not even
> Date: Fri, 16 Sep 2005 01:04:00 +0400
> From: "Ilya N. Golubev" <[EMAIL PROTECTED]>
>
> Version: 6.3
>
> `make distclean' leaves the following files in build directory.
>
> intl/config.h
> intl/config.status
> intl/stamp-h
> gdb/doc/gdb.info
> gdb/doc/gdb.info-1
> gdb/doc/gdb.info-2
> gdb/doc/
> From: Der Herr Hofrat <[EMAIL PROTECTED]>
> Date: Mon, 27 Feb 2006 08:31:14 +0100 (CET)
>
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> Quit this debugging session? (y or n)
> Create a core file of GDB? (y or n) y
> Aborted
>
>
> no core file is gen
> From: Richard Stallman <[EMAIL PROTECTED]>
> Date: Sun, 23 Jul 2006 01:27:11 -0400
>
> In GDB 6.4 on GNU/Linux, I did `i frame' after a strange Emacs crash
> involving stack clobberage. The command did not work, reporting
> "internal error" in dwarf-frame2.c:676. (I am typing this from
> memor
> From: Naresh Vankayalapati <[EMAIL PROTECTED]>
> Date: Thu, 30 Nov 2006 15:24:09 -0500
> Cc:
>
> I wanted to know if there is a way to use these debuggers to debug
> executables generated using MSVC.
You cannot use GDB to debug MSVC-compiled programs on the source
level. GDB doesn't understan
> Date: Sat, 3 Jan 2009 23:45:20 -0800 (PST)
> From: M Jalili
>
> i compile my c program with gcc 4.3.1 by this command:
> gcc -o prog1.out prog1.c -ggdb
> then is use gdb to fetch some information in run time.
> gdb -e prog1.out -s prog1.out
> and when is use "info symbol var1" (var1 is a vari
> From: Jim Meyering
> Date: Wed, 11 Feb 2009 09:56:34 +0100
>
>
> -* Core File Generation::Cause a program dump its core
> +* Core File Generation::Cause a program to dump its core
Are you sure this is incorrect English?
___
bug-gdb
> From: Jim Meyering
> Cc: bug-gdb@gnu.org
> Date: Wed, 11 Feb 2009 21:40:28 +0100
>
> -* Core File Generation::Cause a program dump its core
> +* Core File Generation::Make a program dump its core
That sounds much better, thanks.
___
> Date: Fri, 15 Jun 2012 02:43:35 +0200
> From: Patrice Dumas
> Cc: Karl Berry
>
> Please find attached a patch for the gdb documentation that fixes issues
> such as @itemx instead of @item, empty @item, a missing @node, @menu
> entries order inconsistent with respect with sectioning, and @@ to
> Date: Wed, 20 Jun 2012 22:37:53 +0200
> From: Patrice Dumas
> Cc: Karl Berry
>
> The following warnings remain when using the cvs makeinfo version. It
> is unclear to me how to solve these, but hipefully, you should be able
> to fix them, or bear with warnings:
Thanks, but...
> ./gdb.texinf
> Date: Wed, 20 Jun 2012 22:37:53 +0200
> From: Patrice Dumas
> Cc: Karl Berry
>
> ./gdb.texinfo:11503: warning: @strong{Note...} produces a spurious
> cross-reference in Info
No, it doesn't, not with a colon immediately following the "Note".
___
bu
> Date: Thu, 21 Jun 2012 15:50:29 +0200
> From: Patrice Dumas
> Cc: bug-gdb@gnu.org, k...@freefriends.org
>
> On Thu, Jun 21, 2012 at 05:52:55AM +0300, Eli Zaretskii wrote:
> >
> > > ./gdb.texinfo:22939: warning: @table has text but no @item
> >
> > Wh
> Date: Thu, 21 Jun 2012 15:58:57 +0200
> From: Patrice Dumas
> Cc: bug-gdb@gnu.org, k...@freefriends.org
>
> On Thu, Jun 21, 2012 at 05:56:49AM +0300, Eli Zaretskii wrote:
> > > Date: Wed, 20 Jun 2012 22:37:53 +0200
> > > From: Patrice Dumas
> > >
> Date: Thu, 21 Jun 2012 19:18:19 +0200
> From: Patrice Dumas
> Cc: bug-gdb@gnu.org, k...@freefriends.org
>
> On Thu, Jun 21, 2012 at 07:15:47PM +0300, Eli Zaretskii wrote:
> > > On Thu, Jun 21, 2012 at 05:52:55AM +0300, Eli Zaretskii wrote:
> > > >
&g
> Date: Thu, 21 Jun 2012 19:24:51 +0200
> From: Patrice Dumas
> Cc: bug-gdb@gnu.org, k...@freefriends.org
>
> On Thu, Jun 21, 2012 at 07:17:40PM +0300, Eli Zaretskii wrote:
> > > > > ./gdb.texinfo:11503: warning: @strong{Note...} produces a spurious
>
> Date: Sat, 23 Jun 2012 13:29:38 +0200
> From: Patrice Dumas
> Cc: bug-gdb@gnu.org, k...@freefriends.org
>
> On Thu, Jun 21, 2012 at 10:54:15PM +0300, Eli Zaretskii wrote:
> > >
> > > I don't think so. If I am not wrong, a colon means that there is a lab
> Date: Sat, 23 Jun 2012 15:07:38 +0200
> From: Patrice Dumas
> Cc: bug-gdb@gnu.org, k...@freefriends.org
>
> You missed my point. The manual is formatted fine, but since it uses an
> undocummented Texinfo feature it is in a bad shape Texinfo-wise and the
> formatting could change in the future,
> Date: Tue, 10 Jul 2012 22:39:58 +0200
> From: Patrice Dumas
> Cc: bug-gdb@gnu.org, k...@freefriends.org
>
> On Thu, Jun 21, 2012 at 05:52:55AM +0300, Eli Zaretskii wrote:
> >
> > > ./gdb.texinfo:190: warning: @contents should only appear at beginning or
&
> Date: Tue, 27 Nov 2012 09:01:39 -0800 (PST)
> From: Alexandre Furlan
>
> I have the program a FORTRAN90 and when I debug with gdb, is shown
>
> Program received signal SIGFPE, Arithmetic exception.
> 0x004060be in MAIN__ ()
>
> How to find the line where the error was found ?
Did you
> Date: Tue, 27 Nov 2012 16:14:04 -0200 (BRST)
> From: alexandrepfurlan
> cc: Alexandre Furlan , bug-gdb@gnu.org
>
>
> I tried, and the result is
>
> Program received signal SIGFPE, Arithmetic exception.
> 0x004060be in MAIN__ ()
> (gdb) bt
> #0 0x004060be in MAIN__ ()
>
> And
33 matches
Mail list logo
