, etc).
The maintainers will give you other feedback about format etc.
Michael Snyder
___
bug-gdb mailing list
bug-gdb@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gdb
Markus Plannerer wrote:
>
> Hello,
>
> gdb doesn't work with my application when it comes into the
> function "popen()". After geting information about the
> thread with "info thread" the message "Speicherschutzverletzung"
> comes up and that is the end of gdb. "Speicherschutzverletzung"
> means
Lynn Tinney wrote:
>
> Hi, I'm new and am just trying to get started using gdb 5.2 on Solaris.
> gdb starts fine (gdb program_name) and list and run seem to work fine as
> well, but if I try to set a breakpoint I get "Cannot access memory at
> address 0x...". Can anybody tell me what's going on?
Scott McPeak wrote:
>
> > > I'm working on a project in which some very long (millions of lines) C
> > > source files get generated. Since GNU 'as' and 'gdb' cannot store more
> > > than 16 bits of line number information, debugging programs using these
> > > files is tedious.
>
> > Have you tr
Scott McPeak wrote:
>
> I'm working on a project in which some very long (millions of lines) C
> source files get generated. Since GNU 'as' and 'gdb' cannot store more
> than 16 bits of line number information, debugging programs using these
> files is tedious.
>
> The reason for the 16-bit lim
nagaraja wrote:
>
> hello,
>
> I am running gdbserver (build natively for arm) on target and gdb-5.1
> cross-debuger on host(build with host=i586target=arm-linux) and using
> procedure mensioned in /gdb/gdbserver/REDME
>
> on target machine doing:
> /gdbserver /dev/ttySA0 hello foo.txt
>
> o
[EMAIL PROTECTED] wrote:
>
> Hello!
>
> The problem: I cannot get gdb to remotely debug a program on another machine.
>
> The players: gdb 5.1.1, configured as i386-pc-solaris2.7
>
> The situation: The host and target machines are both Intel boxes running
> Solaris 2.7. I have impleme
Praveen Kumar wrote:
>
> Hi
> I am try to analyse a core dump when running a java
> application.
> I using the command
> gdb /usr/java/bin/sparc/native_threads/java core
>
> info threads
>
> instead of showing the top frame of each thread shows
> addresslocation in ?? ()
>
> I th
Frank Schaefer wrote:
>
> Hi there,
>
> Seems 'set follow-fork-mode' doesn't work for gdb-5.0. See the
> following.
Hi,
I'm afraid "follow-fork" was only implemented on HPUX.
Sorry for the falsely raised expectations...
Perhaps we should do something about hiding those HP-only
features from n
augie wrote:
>
> i read this in the gdb documentation:
>
> Set catchpoints to catch events.
> Raised exceptions may be caught:
> catch throw - all exceptions, when thrown
>
> i read somewhere that when you use this gdb will break when a c++
> exception is thrown, but im no
Eli Zaretskii wrote:
>
> > 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
Shane McDaniel wrote:
>
> I have a program that creates a thread and I would like to be able to use
> two instances of gdb to follow each thread separately, ie the main thread
> and the thread I create. Attaching to the main one is easy enough but how
> do I attach to the second?
In general, t
Cecile Cordier wrote:
>
> Hello,
>
> I am using cygwin from cygnus solution to emulate unix on windows NT.
> I use gcc from cygwin to compile C programs in this environment and I would
> like to debug them using gdb. Unfortunatly I encounter problems doing so.
> Here are the messages I receive:
13 matches
Mail list logo