Opened 10 years ago

Closed 10 years ago

#3769 closed bug (fixed)

Fell into gdb while configuring perl-5.10.0

Reported by: haiqu Owned by: axeld
Priority: normal Milestone: R1
Component: - General Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or 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.
This GDB was configured as "i586-pc-haiku"...(no debugging symbols found)

[tcsetpgrp failed in terminal_inferior: Invalid Argument]
Thread 2500 caused an exception: Segment violation
Reading symbols from /boot/system/runtime_loader...done.
Loaded symbols for /boot/system/runtime_loader
Reading symbols from /boot/system/lib/libroot.so...done.
Loaded symbols for /boot/system/lib/libroot.so
Reading symbols from /boot/home/projects/perl-5.10.0/UU/dyna.so...done.
Loaded symbols for /boot/home/projects/perl-5.10.0/UU/dyna.so
[tcsetpgrp failed in terminal_inferior: Invalid Argument]
[Switching to team ./fred (2500) thread fred (2500)]
0x00201012 in ?? ()
(gdb) 

Not much I could do except close the debug window and continue, I'm unfamiliar with gdb. I'm on hrev30163 right now.

Change History (2)

comment:1 by stippi, 10 years ago

At the GDB prompt, type "bt" which stands for "back trace". That will be equivalent to typing "sc" in the BeOS debugger.

comment:2 by korli, 10 years ago

Resolution: fixed
Status: newclosed

This seems to be fixed when I tested with hrev34939 and perl-5.10.1. Please reopen if needed with the full backtrace.

Note: See TracTickets for help on using tickets.